Wazeopedia wazeopedia_switzerland https://www.waze.com/wiki/Switzerland/Hauptseite MediaWiki 1.36.4 first-letter Medium Spezial Diskussion Benutzer Benutzer Diskussion Wazeopedia Wazeopedia Diskussion Datei Datei Diskussion MediaWiki MediaWiki Diskussion Vorlage Vorlage Diskussion Hilfe Hilfe Diskussion Kategorie Kategorie Diskussion Formular Formular Diskussion Widget Widget Diskussion Campaign Campaign talk Translations Translations talk Gadget Gadget Diskussion Gadget-Definition Gadget-Definition Diskussion 0 1 4551 1 2009-02-18T10:28:20Z MediaWiki default 0 wikitext text/x-wiki <big>'''MediaWiki has been successfully installed.'''</big> Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] bd962048d95fbb6b6b514885867811db20a5476b 0 78 408 407 2012-06-16T21:38:27Z Kentsmith9 25 /* Should the connector be mapped? */ replaced term "ramp" with "connector" to prevent confusion between the two as this is only talking about connectors. wikitext text/x-wiki When traffic moves between two roads that are at the same grade, these connecting segments are not technically ramps to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *when the turn lane physically separates from the main road well in advance of the intersection; *when the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *when the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *As an [[Area Manager]], when you get a user complaint that the audible was too late, or that the map should have shown a connector *in the new editor, if resolving map problems of the type 'The roads are too far apart from each other and most likely a road is missing in between'. This problem would be located at an intersection and the GPS tracks show that the turning lane is far enough from the intersection. in some cases the intersection can be reworked to resolve this problem. When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the lowest of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] 31f36f484e75b5dedbc3d49c38752e4c4c983f6a 410 409 2012-08-10T15:39:26Z Kentsmith9 25 Added the link to the Junction Style Guide article wikitext text/x-wiki When traffic moves between two roads that are at the same grade, these connecting segments are not technically ramps to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *when the turn lane physically separates from the main road well in advance of the intersection; *when the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *when the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *As an [[Area Manager]], when you get a user complaint that the audible was too late, or that the map should have shown a connector *in the new editor, if resolving map problems of the type 'The roads are too far apart from each other and most likely a road is missing in between'. This problem would be located at an intersection and the GPS tracks show that the turning lane is far enough from the intersection. in some cases the intersection can be reworked to resolve this problem. When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speach result. Be sure to review that article when updating or creating these connectors. == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] b6197433f6531ca3665ceb65902c3e69fec38ae3 414 413 2013-02-24T07:32:58Z Kentsmith9 25 Wikilink wikitext text/x-wiki When traffic moves between two roads that are at the same grade, these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *when the turn lane physically separates from the main road well in advance of the intersection; *when the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *when the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *As an [[Area Manager]], when you get a user complaint that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or Allow All Connections function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] 0e5054aa4701ca98b57134dcdc2649d536f0a22d 415 414 2013-03-12T15:07:09Z Kentsmith9 25 wikilinked grade wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *when the turn lane physically separates from the main road well in advance of the intersection; *when the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *when the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *As an [[Area Manager]], when you get a user complaint that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or Allow All Connections function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] 07367b05af7e8a59935fe604715b34ca51f4ab13 10 39 125 2012-06-24T04:38:04Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Your_Rank_and_Points]] ebb60bebb7b8feb8f405a3358ec572a0fb308584 126 125 2013-02-02T19:48:10Z Kentsmith9 25 Redirecting to [[Your Rank and Points]] wikitext text/x-wiki #REDIRECT [[Your Rank and Points]] 79adc1ba465a9c9c645f9a47f90017b65c50473f 0 96 571 570 2012-07-19T21:36:37Z Kentsmith9 25 /* Toll roads */ clarified wikitext text/x-wiki <center>[[Area_Manager#Area_Manager_FAQ|Back to Area Manager FAQ]]</center> Like Waze, this page is a community effort and a work in progress. Many helpful pages already exist on the responsibilities of an [[Area Manager]], how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. At the moment, I am [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=962545 taking suggestions via PM] for content for this page: topic suggestions are good, but links to insightful forum conversations, or even links to other Wiki pages, would be better. I won't be able to incorporate every suggestion, but I will appreciate all of them. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's best to err on the side of caution and disallow the turn. This way, nobody will ever be instructed to make an illegal turn. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. '''Locking should be used sparingly and carefully.''' == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center), the main entrances should be mapped, along with any lanes that run along storefronts, and other lanes that serve to get people from one area of the lot to another. Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped; the rest should be omitted. In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Usability. Simplicity. Your editing time & expertise are much better spent elsewhere. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the loop using two segments.'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not realise it is driveable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' ===Features only available in Cartouche (old editor)=== *Alternate names for segments (currently not referenced, but may have future value) *Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line. Has no effect on routing or client maps whatsoever.) *Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap. *Entering/editing of house numbers (not referenced in basemapped countries). ===Everything listed below refers specifically to Cartouche.=== Every tool, however good, has its limitations, and Cartouche is no exception. For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map. But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them. === Road Geometry and Alternate Names === Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone. It makes no sense, people have been aware of this for ages and it has not been fixed. Perhaps it will be addressed in the next incarnation of the editor. Until then: Nothing to see here, move along. (Just remember to go back and restore the Alt names after the geometry is set. Copy & paste are your friends...) Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions. So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead. === Directionality & Locking === If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly. The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another. When this happens, one-way roads suddenly become two-way. When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation. '''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor. Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way. === The Turn Restrictions Layer is Broken in the Cartouche editor === Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead. === Connectivity === Just because two roads are touching where there is a junction, don't assume they are connected. Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected. To fix, either: * Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut) or * add a junction on top of the existing junction. The new one will replace the old one. Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually. === Reducing Junctions / Consolidating Segments === You will often see junctions in the middle of roads, where there is no intersection. These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads. They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers. In short, unnecessary junctions indicate problems, and should almost always be eliminated. (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.) When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions. If both segments are two-way, or one-way in the same directions, it will work. If they are both "no entrance", it will fail. IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward. After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions. Please note that there are currently [[bugs can occur when deleting junctions]]. === How to Remove Multiple Junctions === During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well. This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged: #Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created. I suspect this is due to a race condition. Deleting adjacent junctions means you are deleting the junctions at both ends of a segment. If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted. #:''The workaround for this bug is to make sure you never multi-delete adjacent junctions. However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:'' #Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate. 4a05ffbf1a1cf7d65827cc7613ea1c434b8a86b8 573 572 2012-08-10T05:33:20Z Kentsmith9 25 Added the link to the Junction Style Guide article wikitext text/x-wiki <center>[[Area_Manager#Area_Manager_FAQ|Back to Area Manager FAQ]]</center> Like Waze, this page is a community effort and a work in progress. Many helpful pages already exist on the responsibilities of an [[Area Manager]], how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. At the moment, I am [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=962545 taking suggestions via PM] for content for this page: topic suggestions are good, but links to insightful forum conversations, or even links to other Wiki pages, would be better. I won't be able to incorporate every suggestion, but I will appreciate all of them. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's best to err on the side of caution and disallow the turn. This way, nobody will ever be instructed to make an illegal turn. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center), the main entrances should be mapped, along with any lanes that run along storefronts, and other lanes that serve to get people from one area of the lot to another. Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped; the rest should be omitted. In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Usability. Simplicity. Your editing time & expertise are much better spent elsewhere. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the loop using two segments.'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not realise it is driveable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' ===Features only available in Cartouche (old editor)=== *Alternate names for segments (currently not referenced, but may have future value) *Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line. Has no effect on routing or client maps whatsoever.) *Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap. *Entering/editing of house numbers (not referenced in basemapped countries). ===Everything listed below refers specifically to Cartouche.=== Every tool, however good, has its limitations, and Cartouche is no exception. For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map. But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them. === Road Geometry and Alternate Names === Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone. It makes no sense, people have been aware of this for ages and it has not been fixed. Perhaps it will be addressed in the next incarnation of the editor. Until then: Nothing to see here, move along. (Just remember to go back and restore the Alt names after the geometry is set. Copy & paste are your friends...) Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions. So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead. === Directionality & Locking === If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly. The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another. When this happens, one-way roads suddenly become two-way. When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation. '''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor. Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way. === The Turn Restrictions Layer is Broken in the Cartouche editor === Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead. === Connectivity === Just because two roads are touching where there is a junction, don't assume they are connected. Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected. To fix, either: * Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut) or * add a junction on top of the existing junction. The new one will replace the old one. Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually. === Reducing Junctions / Consolidating Segments === You will often see junctions in the middle of roads, where there is no intersection. These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads. They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers. In short, unnecessary junctions indicate problems, and should almost always be eliminated. (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.) When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions. If both segments are two-way, or one-way in the same directions, it will work. If they are both "no entrance", it will fail. IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward. After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions. Please note that there are currently [[bugs can occur when deleting junctions]]. === How to Remove Multiple Junctions === During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well. This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged: #Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created. I suspect this is due to a race condition. Deleting adjacent junctions means you are deleting the junctions at both ends of a segment. If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted. #:''The workaround for this bug is to make sure you never multi-delete adjacent junctions. However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:'' #Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate. 961242c28c70e27d87af5ccc7b84b3e39c3a9316 574 573 2012-08-10T06:15:43Z Kentsmith9 25 /* Shopping Centers */ minor clarifications and added example image wikitext text/x-wiki <center>[[Area_Manager#Area_Manager_FAQ|Back to Area Manager FAQ]]</center> Like Waze, this page is a community effort and a work in progress. Many helpful pages already exist on the responsibilities of an [[Area Manager]], how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. At the moment, I am [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=962545 taking suggestions via PM] for content for this page: topic suggestions are good, but links to insightful forum conversations, or even links to other Wiki pages, would be better. I won't be able to incorporate every suggestion, but I will appreciate all of them. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's best to err on the side of caution and disallow the turn. This way, nobody will ever be instructed to make an illegal turn. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center), the main entrances should be mapped, along with any lanes that run along storefronts, and other lanes that serve to get people from one area of the lot to another. Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped; the rest should be omitted. You can turn on the GPS points layer (shortcut key Shift-G) to see where traffic has been most recently to help determine what might be the best section to map. [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the loop using two segments.'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not realise it is driveable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' ===Features only available in Cartouche (old editor)=== *Alternate names for segments (currently not referenced, but may have future value) *Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line. Has no effect on routing or client maps whatsoever.) *Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap. *Entering/editing of house numbers (not referenced in basemapped countries). ===Everything listed below refers specifically to Cartouche.=== Every tool, however good, has its limitations, and Cartouche is no exception. For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map. But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them. === Road Geometry and Alternate Names === Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone. It makes no sense, people have been aware of this for ages and it has not been fixed. Perhaps it will be addressed in the next incarnation of the editor. Until then: Nothing to see here, move along. (Just remember to go back and restore the Alt names after the geometry is set. Copy & paste are your friends...) Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions. So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead. === Directionality & Locking === If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly. The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another. When this happens, one-way roads suddenly become two-way. When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation. '''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor. Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way. === The Turn Restrictions Layer is Broken in the Cartouche editor === Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead. === Connectivity === Just because two roads are touching where there is a junction, don't assume they are connected. Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected. To fix, either: * Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut) or * add a junction on top of the existing junction. The new one will replace the old one. Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually. === Reducing Junctions / Consolidating Segments === You will often see junctions in the middle of roads, where there is no intersection. These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads. They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers. In short, unnecessary junctions indicate problems, and should almost always be eliminated. (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.) When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions. If both segments are two-way, or one-way in the same directions, it will work. If they are both "no entrance", it will fail. IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward. After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions. Please note that there are currently [[bugs can occur when deleting junctions]]. === How to Remove Multiple Junctions === During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well. This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged: #Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created. I suspect this is due to a race condition. Deleting adjacent junctions means you are deleting the junctions at both ends of a segment. If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted. #:''The workaround for this bug is to make sure you never multi-delete adjacent junctions. However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:'' #Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate. c9c22450e0a3127da6a1060a4a3a632398dc484c 575 574 2012-08-10T23:53:10Z Kentsmith9 25 updated into to be more universal wikitext text/x-wiki The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's best to err on the side of caution and disallow the turn. This way, nobody will ever be instructed to make an illegal turn. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center), the main entrances should be mapped, along with any lanes that run along storefronts, and other lanes that serve to get people from one area of the lot to another. Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped; the rest should be omitted. You can turn on the GPS points layer (shortcut key Shift-G) to see where traffic has been most recently to help determine what might be the best section to map. [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the loop using two segments.'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not realise it is driveable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' ===Features only available in Cartouche (old editor)=== *Alternate names for segments (currently not referenced, but may have future value) *Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line. Has no effect on routing or client maps whatsoever.) *Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap. *Entering/editing of house numbers (not referenced in basemapped countries). ===Everything listed below refers specifically to Cartouche.=== Every tool, however good, has its limitations, and Cartouche is no exception. For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map. But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them. === Road Geometry and Alternate Names === Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone. It makes no sense, people have been aware of this for ages and it has not been fixed. Perhaps it will be addressed in the next incarnation of the editor. Until then: Nothing to see here, move along. (Just remember to go back and restore the Alt names after the geometry is set. Copy & paste are your friends...) Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions. So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead. === Directionality & Locking === If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly. The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another. When this happens, one-way roads suddenly become two-way. When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation. '''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor. Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way. === The Turn Restrictions Layer is Broken in the Cartouche editor === Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead. === Connectivity === Just because two roads are touching where there is a junction, don't assume they are connected. Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected. To fix, either: * Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut) or * add a junction on top of the existing junction. The new one will replace the old one. Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually. === Reducing Junctions / Consolidating Segments === You will often see junctions in the middle of roads, where there is no intersection. These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads. They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers. In short, unnecessary junctions indicate problems, and should almost always be eliminated. (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.) When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions. If both segments are two-way, or one-way in the same directions, it will work. If they are both "no entrance", it will fail. IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward. After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions. Please note that there are currently [[bugs can occur when deleting junctions]]. === How to Remove Multiple Junctions === During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well. This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged: #Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created. I suspect this is due to a race condition. Deleting adjacent junctions means you are deleting the junctions at both ends of a segment. If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted. #:''The workaround for this bug is to make sure you never multi-delete adjacent junctions. However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:'' #Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate. b559874726cc1840c305e31563d7c04b99f30f4e 577 576 2012-09-04T03:14:17Z Kentsmith9 25 /* Shopping Centers */ clarification wikitext text/x-wiki The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and allow the turn. This way, waze will always give an optimal route and the driver can decide (based on local conditions) whether or not to use it. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the loop using two segments.'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not realise it is driveable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' ===Features only available in Cartouche (old editor)=== *Alternate names for segments (currently not referenced, but may have future value) *Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line. Has no effect on routing or client maps whatsoever.) *Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap. *Entering/editing of house numbers (not referenced in basemapped countries). ===Everything listed below refers specifically to Cartouche.=== Every tool, however good, has its limitations, and Cartouche is no exception. For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map. But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them. === Road Geometry and Alternate Names === Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone. It makes no sense, people have been aware of this for ages and it has not been fixed. Perhaps it will be addressed in the next incarnation of the editor. Until then: Nothing to see here, move along. (Just remember to go back and restore the Alt names after the geometry is set. Copy & paste are your friends...) Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions. So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead. === Directionality & Locking === If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly. The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another. When this happens, one-way roads suddenly become two-way. When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation. '''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor. Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way. === The Turn Restrictions Layer is Broken in the Cartouche editor === Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead. === Connectivity === Just because two roads are touching where there is a junction, don't assume they are connected. Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected. To fix, either: * Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut) or * add a junction on top of the existing junction. The new one will replace the old one. Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually. === Reducing Junctions / Consolidating Segments === You will often see junctions in the middle of roads, where there is no intersection. These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads. They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers. In short, unnecessary junctions indicate problems, and should almost always be eliminated. (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.) When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions. If both segments are two-way, or one-way in the same directions, it will work. If they are both "no entrance", it will fail. IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward. After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions. Please note that there are currently [[bugs can occur when deleting junctions]]. === How to Remove Multiple Junctions === During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well. This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged: #Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created. I suspect this is due to a race condition. Deleting adjacent junctions means you are deleting the junctions at both ends of a segment. If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted. #:''The workaround for this bug is to make sure you never multi-delete adjacent junctions. However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:'' #Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate. 86f50159ab4c0cbe002693c95de3060937897564 578 577 2012-09-04T03:17:05Z Kentsmith9 25 /* Drive-Through Lots */ Wikilink wikitext text/x-wiki The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and allow the turn. This way, waze will always give an optimal route and the driver can decide (based on local conditions) whether or not to use it. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not realise it is driveable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' ===Features only available in Cartouche (old editor)=== *Alternate names for segments (currently not referenced, but may have future value) *Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line. Has no effect on routing or client maps whatsoever.) *Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap. *Entering/editing of house numbers (not referenced in basemapped countries). ===Everything listed below refers specifically to Cartouche.=== Every tool, however good, has its limitations, and Cartouche is no exception. For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map. But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them. === Road Geometry and Alternate Names === Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone. It makes no sense, people have been aware of this for ages and it has not been fixed. Perhaps it will be addressed in the next incarnation of the editor. Until then: Nothing to see here, move along. (Just remember to go back and restore the Alt names after the geometry is set. Copy & paste are your friends...) Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions. So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead. === Directionality & Locking === If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly. The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another. When this happens, one-way roads suddenly become two-way. When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation. '''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor. Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way. === The Turn Restrictions Layer is Broken in the Cartouche editor === Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead. === Connectivity === Just because two roads are touching where there is a junction, don't assume they are connected. Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected. To fix, either: * Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut) or * add a junction on top of the existing junction. The new one will replace the old one. Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually. === Reducing Junctions / Consolidating Segments === You will often see junctions in the middle of roads, where there is no intersection. These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads. They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers. In short, unnecessary junctions indicate problems, and should almost always be eliminated. (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.) When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions. If both segments are two-way, or one-way in the same directions, it will work. If they are both "no entrance", it will fail. IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward. After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions. Please note that there are currently [[bugs can occur when deleting junctions]]. === How to Remove Multiple Junctions === During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well. This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged: #Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created. I suspect this is due to a race condition. Deleting adjacent junctions means you are deleting the junctions at both ends of a segment. If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted. #:''The workaround for this bug is to make sure you never multi-delete adjacent junctions. However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:'' #Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate. d8fc4b00474ef1c8bed47f2c3dc1799bc187df34 579 578 2012-09-04T03:18:42Z Kentsmith9 25 /* Recorded via Client */ Universal words wikitext text/x-wiki The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and allow the turn. This way, waze will always give an optimal route and the driver can decide (based on local conditions) whether or not to use it. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' ===Features only available in Cartouche (old editor)=== *Alternate names for segments (currently not referenced, but may have future value) *Removal of separating line (obsolete feature, but useful for getting rid of the black line on the Primary Street segments, which may make it difficult to see arrows which indicate the directionality of the segment - also for the sanity of editors who can't stand the sight of that black line. Has no effect on routing or client maps whatsoever.) *Viewing of Update Requests sent prior to February 2012, or URs that have been sent via LiveMap. *Entering/editing of house numbers (not referenced in basemapped countries). ===Everything listed below refers specifically to Cartouche.=== Every tool, however good, has its limitations, and Cartouche is no exception. For general editing, what you see is usually what you get, and if you read the copious online documentation in advance, you will be able to make sense of (and extricate yourself from) most situations that you run into when editing the map. But there are a few things to watch out for, that can result in a lot of extra work for you if you miss them. === Road Geometry and Alternate Names === Simply put: when you edit the geometry of a road, any Alternate names assigned to it are gone. It makes no sense, people have been aware of this for ages and it has not been fixed. Perhaps it will be addressed in the next incarnation of the editor. Until then: Nothing to see here, move along. (Just remember to go back and restore the Alt names after the geometry is set. Copy & paste are your friends...) Note that this only affects the segment whose geometry is actually being modified, and ''not'' any roads that might be connected to it via junctions. So if you have a road with an Alt name (e.g., a minor highway), you may be able to adjust its geometry without disturbing its Alt name assignment by editing the geometry of adjoining roads instead. === Directionality & Locking === If Waze sees enough people driving along a road in a certain direction, it will conclude that travel in that direction is allowed, and update the map accordingly. The problem is, client GPS signals can be inaccurate, and Waze can mistakenly think that you are on one road when you are really on another. When this happens, one-way roads suddenly become two-way. When this happens on a highway or one of its ramps, it can have far-reaching effects on navigation. '''UPDATE:''' Waze has changed its heuristics to make it more difficult for road directionality to change as described above, once it has been set via the editor. Therefore, in order to allow automatic geometry adjustments, it is now better to leave roads unlocked after assigned them to be one-way. === The Turn Restrictions Layer is Broken in the Cartouche editor === Just leave this layer off and use the [[Cartouche_-_Update_map#Highlight_Connectivity:|Highlight Connectivity]] feature instead. === Connectivity === Just because two roads are touching where there is a junction, don't assume they are connected. Because you have "Highlight Connectivity" turned on (see above), you should notice pretty quickly that a segment is not connected. To fix, either: * Highlight the disconnected segment and the one to which it needs to connect, in from-to order where one-way roads are involved, and use "Connect roads in order of selection" (or the 'c' keyboard shortcut) or * add a junction on top of the existing junction. The new one will replace the old one. Most of the time you will want the "Allow all turns" mode on, but sometimes when working with one-way roads it is easier to turn that option off and enable turns individually. === Reducing Junctions / Consolidating Segments === You will often see junctions in the middle of roads, where there is no intersection. These "extra" junctions are often the result of editing attempts gone awry, and seem to be a magnet for ill-connected and incorrectly-named roads. They multiply the number of segments that you need to maintain, and I'm sure they're not helpful to the routing servers. In short, unnecessary junctions indicate problems, and should almost always be eliminated. (The only exceptions are when they mark a change of city, or when you know that you will be connecting a road there very soon.) When deleting a junction, remember that the segments on either side of the junction have to match road type, name, city, state, and have compatible directions. If both segments are two-way, or one-way in the same directions, it will work. If they are both "no entrance", it will fail. IMO this is a bug; just remember to change them to two-way beforehand, and then change the consolidated segment back to "no entrance" afterward. After the junctions are removed, you may need to adjust the consolidated segment's geometry to account for the missing junctions. Please note that there are currently [[bugs can occur when deleting junctions]]. === How to Remove Multiple Junctions === During the interval after pressing the 'y' key (to confirm removing a junction) and before Cartouche returns control to the Edit Panel, it ''is'' possible to click on additional junctions and use the 'y' key to delete them as well. This often results in faster deletions because Cartouche is effectively deleting them in parallel; '''However,''' there is one known bug and one suspected bug associated with this practice, so its use is highly discouraged: #Deleting adjacent junctions in this manner often causes nearby road segments to vanish, and need to be re-created. I suspect this is due to a race condition. Deleting adjacent junctions means you are deleting the junctions at both ends of a segment. If the first junction is deleted, and then before the segment can be merged with its neighbor, the second junction is deleted, the road segment between them ends up being deleted. #:''The workaround for this bug is to make sure you never multi-delete adjacent junctions. However, I have started to suspect another bug that has sworn me off of multi-deleting junctions at all, adjacent or not:'' #Also probably due to a race condition, I believe that using this technique may corrupt the segment IDs of the road segments involved, causing route highlighting problems when using the Waze client to navigate. e329f152803669f1169d164c0dee21aaf9f4ad6d 580 579 2012-09-04T03:29:31Z Kentsmith9 25 Noted where the Cartouche data was moved wikitext text/x-wiki The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === It is not always a good idea to split anything short of a freeway or major highway--which use nothing but ramps to enter/exit--into two one-way roads. Some formal guidelines - '''A road should be split if:''' * There is at least 5 meters of non-drivable surface between directions of travel. (This means a median of some type like cement, planter boxes, trees, or just grass. * GPS tracks show a clearly definable gap/blank area between the color-by-azimuth arrows at the 100m zoom level. * A road with a non-drivable surface (of any width) between the directions of travel where many left turns are physically impossible due to the median. * A road with a non-drivable surface (of any width) between the directions of travel where there are three or more lanes in each travel direction. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should not be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane, even a wide one, between directions of travel, does not count because it is drivable. * Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. (I strongly believe that, for every mile of road that an AM wants to split into one-way roads, he should first merge a mile of split roads back into a two-way road. [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Check out what's involved]]. It builds character.) === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and allow the turn. This way, waze will always give an optimal route and the driver can decide (based on local conditions) whether or not to use it. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' The old information on Cartouche has been moved to [[Best map editing practice (Cartouche)]] for archive purposes. 65640263ad65b0d51df724c414a1fbbb1387c582 581 580 2012-09-15T06:03:41Z Kentsmith9 25 /* When (Not) to Split a Two-Way Road */ Updates per http://www.waze.com/forum/viewtopic.php?f=212&t=26083 wikitext text/x-wiki The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road it is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at every intersection. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and allow the turn. This way, waze will always give an optimal route and the driver can decide (based on local conditions) whether or not to use it. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' The old information on Cartouche has been moved to [[Best map editing practice (Cartouche)]] for archive purposes. 968f22f5f30e971c8082119a85202dafcdc806b0 582 581 2012-09-17T21:58:29Z Kentsmith9 25 /* When (Not) to Split a Two-Way Road */ "most intersections" wikitext text/x-wiki The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road it is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and allow the turn. This way, waze will always give an optimal route and the driver can decide (based on local conditions) whether or not to use it. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]] in Cartouche, it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. Note that a roundabout should never be used in place of an end-node on dead-end or cul-de-sac streets. === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === Even though a proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in Cartouche, when it is first created, the segments are configured as new roads. They will need to be edited as above before they will become part of the live map. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] == Cartouche (old editor) Caveats == '''''Cartouche has been superseded by Waze Map Editor (WME) and should only be used by experienced map editors to access a few features that are not available in WME. As of January 2012, Waze developers have expressed their intention of taking this editor offline, but they have not done so because of these few unavailable features in WME. Many of the problems listed in this section have been solved with WME.''''' The old information on Cartouche has been moved to [[Best map editing practice (Cartouche)]] for archive purposes. 90c1c9b5aaff9e3993454ce7bcb8421fe7887b7a 595 594 2013-02-23T20:20:56Z Kentsmith9 25 /* Caveat re. Levels */ links to deleting a junction and road levels wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road it is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing HOV lanes and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and '''restrict''' the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 0c3c6bfa11303ca2971a21b4528f8420a9a8455d 596 595 2013-02-27T05:44:50Z Kentsmith9 25 /* Time Restricted Turns */ moved to template for use in multiple locations wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road it is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing HOV lanes and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 609e599e595effd35fcf9078f86720457198df33 598 597 2013-03-26T05:14:24Z Kentsmith9 25 Undo revision 32994 by [[Special:Contributions/Aaronsta|Aaronsta]] ([[User talk:Aaronsta|Talk]]) Left talk page message to not do this wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road it is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing HOV lanes and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 609e599e595effd35fcf9078f86720457198df33 599 598 2013-03-26T05:19:44Z Kentsmith9 25 Tranfered changes from incorrectly named page wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 3ceb3943c717b43a2abcf4cc3d9a0d413369a40b 0 89 467 466 2012-07-20T06:03:36Z Kentsmith9 25 Moved servers to a table wikitext text/x-wiki Waze uses at least three different banks of servers. {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Server URL |- | USA & Canada | http://www.waze.com |- | Isreal | http://www.waze.co.il/ |- | Rest of World | http://world.waze.com |} These function independently of each other, so please specify which one you use when asking questions or reporting issues. If you visit http://www.waze.com , it should automatically switch you to the correct server. In case the server does not correctly forward you to the right server (for example [[Dashboard]] or [[Map_Editing_(new_Editor)#Editing_Manual|Waze Map Editor]] is not showing the correct amount of points or routes), use one of the links above. 3abd7503f67005e288ae5be28d07bfceb9da8614 469 468 2012-08-10T23:05:06Z Kentsmith9 25 added more information wikitext text/x-wiki Waze uses at least three different banks of servers. {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Server URL |- | USA & Canada | http://www.waze.com |- | Israel | http://www.waze.co.il/ |- | Rest of World | http://world.waze.com |} These function independently of each other, so please specify which one you use when asking questions or reporting issues. All maps for each region listed above are separate. Anything reported or created on one of these servers will not be visible on the others. Note that you do have a login automatically created on the different servers, so you can mistakenly log into the wrong server and not realize it until you look for your points, groups or prior map changes. You may find map changes in one server for an area covered by another. This might make you think you are on the right server, but that area is not kept in sync with the primary server. At this time that area is not used by the client app and serves no purpose so do not bother making any changes to it. If you visit http://www.waze.com , it should automatically switch you to the correct server. In case the server does not correctly forward you to the right server (for example [[Dashboard]] or [[Map_Editing_(new_Editor)#Editing_Manual|Waze Map Editor]] is not showing the correct amount of points or routes), use one of the links above. e00fdc93d787dee609e3997416fb1197e33a0a36 470 469 2012-08-12T18:20:39Z Kentsmith9 25 Added procedure for moving the client to the appropriate server wikitext text/x-wiki Waze uses at least three different banks of servers. {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Server URL |- | USA & Canada | http://www.waze.com |- | Israel | http://www.waze.co.il/ |- | Rest of the World | http://world.waze.com |} These function independently of each other, so please specify which one you use when asking questions or reporting issues. == Overview == All maps for each region listed above are separate. Anything reported or created on one of these servers will not be visible on the others. Note that you do have a login automatically created on the different servers, so you can mistakenly log into the wrong server and not realize it until you look for your points, groups or prior map changes. You may find map changes in one server for an area covered by another. This might make you think you are on the right server, but that area is not kept in sync with the primary server. At this time that area is not used by the client app and serves no purpose so do not bother making any changes to it. If you visit http://www.waze.com , it should automatically switch you to the correct server. In case the server does not correctly forward you to the right server (for example [[Dashboard]] or [[Map_Editing_(new_Editor)#Editing_Manual|Waze Map Editor]] is not showing the correct amount of points or routes), use one of the links above. == Fixing server link for client application == If the client application jumps to the wrong server by mistake (it has happened to a few people in the paste) you might not be able to see your points. To fix it, start the Waze application on the client and try to login with your local account. If this fails: * Login with a temporary account (by clicking skip button from the Sign Up menu) * Go to Navigate from the main menu and from the '''search for address bar''' enter one of the following character sequences to move the the server for your area {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Search for |- | USA & Canada | <nowiki>##@usa</nowiki> |- | Israel | <nowiki>##@il</nowiki> |- | Rest of the World | <nowiki>##@other</nowiki> |} * Restart the application and enter your original login information 642182781572877eff9d30e4994d5b612d703ef9 472 471 2013-02-25T16:20:02Z Kentsmith9 25 /* Fixing server link for client application */ data on relocating between continents wikitext text/x-wiki Waze uses at least three different banks of servers. {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Server URL |- | USA & Canada | http://www.waze.com |- | Israel | http://www.waze.co.il/ |- | Rest of the World | http://world.waze.com |} These function independently of each other, so please specify which one you use when asking questions or reporting issues. == Overview == All maps for each region listed above are separate. Anything reported or created on one of these servers will not be visible on the others. Note that you do have a login automatically created on the different servers, so you can mistakenly log into the wrong server and not realize it until you look for your points, groups or prior map changes. You may find map changes in one server for an area covered by another. This might make you think you are on the right server, but that area is not kept in sync with the primary server. At this time that area is not used by the client app and serves no purpose so do not bother making any changes to it. If you visit http://www.waze.com , it should automatically switch you to the correct server. In case the server does not correctly forward you to the right server (for example [[Dashboard]] or [[Map_Editing_(new_Editor)#Editing_Manual|Waze Map Editor]] is not showing the correct amount of points or routes), use one of the links above. == Fixing server link for client application == If the client application jumps to the wrong server by mistake (it has happened to a few people in the past) you might not be able to see your points. If you take your mobile phone or smart device from the US to Europe or vis-a-versa, you may need to force the client to switch to an alternate server. In both of the above cases, start the Waze application on the client and try to login with your local account. If this fails: * Login with a temporary account (by clicking skip button from the Sign Up menu) * Go to Navigate from the main menu and from the '''search for address bar''' enter one of the following character sequences to move the the server for your area {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Search for |- | USA & Canada | <nowiki>##@usa</nowiki> |- | Israel | <nowiki>##@il</nowiki> |- | Rest of the World | <nowiki>##@other</nowiki> |} * Restart the application and enter your original login information 0cfc4394dfccd8adf85ae6f260918e21cec37f91 473 472 2013-03-11T07:00:28Z Kentsmith9 25 Added alternate names used for the servers wikitext text/x-wiki Waze uses at least three different banks of servers. {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Alternate Name ! Server URL |- | USA & Canada | North America | http://www.waze.com |- | Israel | (none) | http://www.waze.co.il/ |- | Rest of the World | World | http://world.waze.com |} These function independently of each other, so please specify which one you use when asking questions or reporting issues. Note the servers in Israel are being migrated to the World servers and will eventually be taken down. == Overview == All maps for each region listed above are separate. Anything reported or created on one of these servers will not be visible on the others. Note that you do have a login automatically created on the different servers, so you can mistakenly log into the wrong server and not realize it until you look for your points, groups or prior map changes. You may find map changes in one server for an area covered by another. This might make you think you are on the right server, but that area is not kept in sync with the primary server. At this time that area is not used by the client app and serves no purpose so do not bother making any changes to it. If you visit http://www.waze.com , it should automatically switch you to the correct server. In case the server does not correctly forward you to the right server (for example [[Dashboard]] or [[Map_Editing_(new_Editor)#Editing_Manual|Waze Map Editor]] is not showing the correct amount of points or routes), use one of the links above. == Fixing server link for client application == If the client application jumps to the wrong server by mistake (it has happened to a few people in the past) you might not be able to see your points. If you take your mobile phone or smart device from the US to Europe or vis-a-versa, you may need to force the client to switch to an alternate server. In both of the above cases, start the Waze application on the client and try to login with your local account. If this fails: * Login with a temporary account (by clicking skip button from the Sign Up menu) * Go to Navigate from the main menu and from the '''search for address bar''' enter one of the following character sequences to move the the server for your area {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Search for |- | USA & Canada | <nowiki>##@usa</nowiki> |- | Israel | <nowiki>##@il</nowiki> |- | Rest of the World | <nowiki>##@other</nowiki> |} * Restart the application and enter your original login information 1a15c1d18c2280afcfe9ca2255c5828d4d4c6bb5 10 36 11454 2012-08-04T04:17:30Z Kentsmith9 25 Creating template for Anchors wikitext text/x-wiki {{#if:{{{1|}}}|<span id="{{{1|}}}"></span>}}<!-- -->{{#if:{{{2|}}}|<span id="{{{2|}}}"></span>}}<!-- -->{{#if:{{{3|}}}|<span id="{{{3|}}}"></span>}}<!-- -->{{#if:{{{4|}}}|<span id="{{{4|}}}"></span>}}<!-- -->{{#if:{{{5|}}}|<span id="{{{5|}}}"></span>}}<!-- -->{{#if:{{{6|}}}|<span id="{{{6|}}}"></span>}}<!-- -->{{#if:{{{7|}}}|<span id="{{{7|}}}"></span>}}<!-- -->{{#if:{{{8|}}}|<span id="{{{8|}}}"></span>}}<!-- -->{{#if:{{{9|}}}|<span id="{{{9|}}}"></span>}}<!-- -->{{#if:{{{10|}}}|<span id="{{{10|}}}"></span>}}<!-- -->{{#if:{{{11|}}}|<span class="error">[[Template:Anchor]] (or Anchors): too many anchors, maximum is 10.</span>}} dd3fa07577aa8a478c5c310a691ae45bcc2ed7ef 11455 11454 2012-08-04T04:19:13Z Kentsmith9 25 commented it out until someone with more skill can properly create it wikitext text/x-wiki <!-- Fail. Maybe someone with more Template Creation experience can create this template {{#if:{{{1|}}}|<span id="{{{1|}}}"></span>}}<!-- -->{{#if:{{{2|}}}|<span id="{{{2|}}}"></span>}}<!-- -->{{#if:{{{3|}}}|<span id="{{{3|}}}"></span>}}<!-- -->{{#if:{{{4|}}}|<span id="{{{4|}}}"></span>}}<!-- -->{{#if:{{{5|}}}|<span id="{{{5|}}}"></span>}}<!-- -->{{#if:{{{6|}}}|<span id="{{{6|}}}"></span>}}<!-- -->{{#if:{{{7|}}}|<span id="{{{7|}}}"></span>}}<!-- -->{{#if:{{{8|}}}|<span id="{{{8|}}}"></span>}}<!-- -->{{#if:{{{9|}}}|<span id="{{{9|}}}"></span>}}<!-- -->{{#if:{{{10|}}}|<span id="{{{10|}}}"></span>}}<!-- -->{{#if:{{{11|}}}|<span class="error">[[Template:Anchor]] (or Anchors): too many anchors, maximum is 10.</span>}} --> 324691970dcd7bfac6cb99fe29776a80e9ae2e40 10 75 349 348 2012-08-18T23:01:55Z Kentsmith9 25 Added note the AM role is under review and to look in the forums for more info wikitext text/x-wiki <span style="color: red;">''The specific details of the Area Manager role are currently under review within the Waze community. Some of the information below is currently out of date. Please review the [http://www.waze.com/forum forums] for more information. Once the role changes are finalized, this section will be updated as required.''</span><br> An Area Manager is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Make changes to the map when road construction projects complete and road geometry needs to be changed, or roads added or removed from the map. * Edit road construction areas, especially for closures so that users are not routed into those areas. * Respond to and act on Update Requests from Waze drivers. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Process and resolve Map Errors or Problems as shown on that layer in the Waze Map Editor. * Act as a mentor to other editors, offering advice in both the forums and when you see improper edits on the map. ==How to Become an Area Manager== ''The Area Manager role '' To become an Area Manager, use [[Map_Editing_(new_Editor)|the Waze Map Editor]] and position the map and set the zoom level to show the area you want to manage. Click on [[Map_Editing_(new_Editor)#Permalink|Permalink]] and then copy the address from the address bar in your browser. Fill out the form [https://docs.google.com/a/waze.com/spreadsheet/viewform?formkey=dGl6TVF2bzFtdHRWUDVzR3N5TllZanc6MA#gid=0 here]and submit. There can be more than one Area Manager in the same area. Areas can overlap, or be smaller or larger. And you can be the Area Manager for more than one area. == Join the community on the Area Manager Display Map == '''While this has no affect on your ability to edit in Waze''', consider adding yourself to the [http://g.co/maps/bnvna Waze Area Manager Global Map on Google maps] once you have received your Area Manager access! Join the community of Waze editors by showing your presence here and [http://www.waze.com/forum joining in the discussion on the forum]. Add a pin for your approximate location and a shape for your approximate Waze AM area on the [http://g.co/maps/f59ur editable version of the Google map]. Please note that this version of the Google map will only show a limited number of pins/shapes "per page", so don't fret if you don't see anyone else around! Also, all changes to this map are live, so be careful not to delete or change anyone else's stuff. To add your pin to the Google map: * From the [http://g.co/maps/f59ur "Editable Google Map"], zoom in on your location * On the left panel of the screen, click on the "Edit" button * In the top left of the map, click on the blue icon * Set your pin on your approximate location * Add your Waze userid as the "Title" and any extra information you would like to provide in the description * On the left panel of the screen, click on the "Done" button To add your Waze AM area to the Google map: * From the [http://g.co/maps/f59ur "Editable Google Map"], zoom in on your location * On the left panel of the screen, click on the "Edit" button * In the top left of the map, click on the small down triangle next to the line icon * Mouse click to set the points of your approximate AM area * Add your Waze userid + AM as the "Title" and any extra information you would like to provide in the description * On the left panel of the screen, click on the "Done" button [http://g.co/maps/bnvna WELCOME TO THE CLUB!] ==Area Manager FAQ== * [[Area Manager: 101]] * [[Map Editing (new_Editor)|Map Editing]] * [[Area Manager: Diagnosis]] * [[Area Manager: Tips and Tricks]] * [[Area Manager: YouTube Training Videos]] * [[Area Manager: How to edit wiki pages]] * [[Best map editing practice]] * [[Known issues]] ===Area Manager To Do lists - Map Editing=== * [[To Do lists - Major Cities]] * [[To Do lists - Country-State-Province]] * [[To Do lists - POI Categories]] ee3a98353c7ce5a47c72f5cc5ccc6abe54a89716 14 110 713 2012-08-29T03:27:31Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road]] 7e97867a887656192e45f32845e543dfba4087ab 714 713 2013-03-11T07:42:33Z Kentsmith9 25 Redirecting to [[Best Map Editing Practice#When .28Not.29 to Split a Two-Way Road]] wikitext text/x-wiki #REDIRECT [[Best_Map_Editing_Practice#When_.28Not.29_to_Split_a_Two-Way_Road]] c404f735014b2e1a35fdce30fc82aa6f4618fab0 715 714 2013-03-26T05:22:22Z Kentsmith9 25 Moved to original page wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road]] 7e97867a887656192e45f32845e543dfba4087ab 0 108 711 2012-10-21T16:13:25Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#Parking_Lots]] 1530347befdd3b3565d9447ec640e15f0ff18f99 8 109 712 2013-01-19T03:58:33Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road]] 7e97867a887656192e45f32845e543dfba4087ab 0 27 74 2013-02-23T18:22:26Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Level''' may refer to: * [[Creating_and_Editing_street_segments#Road_Level|Road Level]], the relative altitude of the road to other roads nearby * Editing Level, [[Points#Map_editing_rank|Map Editing Rank]] relative to other editors * Zoom Level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] {{Disambig}} e5da0066a02c883bdc74aa43d6166e61fdb4ee61 75 74 2013-02-24T00:29:38Z Kentsmith9 25 grammer wikitext text/x-wiki '''Level''' may refer to: * [[Creating_and_Editing_street_segments#Road_Level|Road Level]], the relative altitude of the road compared to other roads nearby * Editing Level, [[Points#Map_editing_rank|Map Editing Rank]] relative to other editors * Zoom Level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] {{Disambig}} 4260f6d964c79ad8193e66075af2ad527cb485c9 6 106 709 2013-02-24T07:23:37Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#Parking_Lots]] 1530347befdd3b3565d9447ec640e15f0ff18f99 0 104 707 2013-02-24T07:25:06Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#Parking_Lots]] 1530347befdd3b3565d9447ec640e15f0ff18f99 0 95 484 2013-02-25T16:20:54Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Banks_of_Servers]] 00369c3b6c6aeb021b97db63aa2d5002f4d538f2 0 91 480 2013-02-25T16:27:16Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Banks_of_Servers]] 00369c3b6c6aeb021b97db63aa2d5002f4d538f2 0 94 483 2013-03-10T06:23:19Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Banks_of_Servers]] 00369c3b6c6aeb021b97db63aa2d5002f4d538f2 0 77 398 2013-03-10T06:25:32Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Area_Manager]] 17c6a8fcc22966685fe2f477307ea1cf8d570739 0 98 697 696 2013-03-11T15:46:45Z Kentsmith9 25 /* Bridging Roads */ comment on Railroads with wikilink wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road it is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing HOV lanes and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and '''restrict''' the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] cd38ddc8fd9b0211e312ea253931f5cde1e6e40f 698 697 2013-03-12T15:10:50Z Kentsmith9 25 /* High Occupancy Toll (HOT) Roads/Lanes (USA) */ wikilink wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === When (Not) to Split a Two-Way Road === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road it is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed descriptions of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other info. of each pair of road segments match. At that point, deleting the junction will most likely work. If not (perhaps because a ramp or another road segment prevents you from deleting it), you can try: ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === Waze currently has no provision for handling this type of restriction, although it is planned for the future. In a situation where a turn is illegal during certain times of the day (e.g. No Left Turn, 7-10 am, 3-7 pm, Weekdays), it's generally best to err on the side of caution and '''restrict''' the turn. This way, waze will never instruct a driver to make a turn when it is illegal (typically during rush-hour traffic, the worst-possible time to create driver confusion). One consequence of restricting such turns will be the generation of Map Problems and Update Requests, indicating that the turn is allowed at certain times. Map Problems should be marked as "Solved", because the cause is known and the map is correct. Update Requests should be resolved as "Not identified", since "Solved" would reply to the human reporter that the issue was fixed (which is not possible in the way the reporter would expect), and since there is no way at present to send an explanation. Because these unresolved problems will invite people to log onto WME and look at the situation for themselves, it is advisable to lock the segments adjacent to a time-restricted turn, to prevent inexperienced editors who do not fully understand the issue from "fixing" the turn. === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 7eefe5db5b947d6b6bbdef774f3d489dfe847112 0 24 67 2013-03-12T15:25:27Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Junction_Style_Guide]] 38028bda434e5351f786597e8c1c6659e9a9eb20 0 14 33 2013-03-12T15:28:28Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Junction_Style_Guide]] 38028bda434e5351f786597e8c1c6659e9a9eb20 0 26 73 2013-03-12T15:29:09Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Junction_Style_Guide]] 38028bda434e5351f786597e8c1c6659e9a9eb20 0 92 481 2013-03-13T05:27:05Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Banks_of_Servers]] 00369c3b6c6aeb021b97db63aa2d5002f4d538f2 0 93 482 2013-03-13T05:27:33Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Banks_of_Servers]] 00369c3b6c6aeb021b97db63aa2d5002f4d538f2 0 8 10563 10562 2013-03-24T22:45:49Z Kentsmith9 25 Updated house numbers wikilink wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutsch|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung:== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Oberfläche und Steuerelemente]] * [[WME Tipps und Tricks]] * [[WME Update Requests]] * [[WME Map Problems]] ==Details zur Bearbeitung:== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Erstellen und bearbeiten von Landmarks]] * [[Unterführungen und Brücken]] * [[Blitzer einpflegen]] * [[Base Map 1.0]] * [[Der Area Manager]] * [[Übersetzung der Landmarks]] ==Seiten auf Englisch== * [[How Waze determines turn / keep / exit maneuvers]] * [[Limited Access Interchange Style Guide]] * [[Navigation problems]] * [[Fixing "smudged" cities]] - [[Verstreute Orte]], in Übersetzung * [[Community Plugins, Extensions and Tools]] * [[House_Numbers_in_WME|House Numbers in Waze Map Editor]] ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Hilf mit Waze zu verbessern]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] (im Aufbau) ==Fehler melden:== * [http://bit.ly/saGRdE Error reporting] - Formular zum Melden von WME Performance-Problemen * [http://bit.ly/vQlGJT Outdated Aerials] - Formular zum Melden von veralteten oder fehlenden Aerials * [https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dDBzTnJ4MEYzeWxKMEhOa0tVbThsVFE6MQ Gas Station Brands] - Formular zum Melden von fehlenden Brands * [https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dGlLcFd1V1dkZW41Y0lKMTJMaXZTUEE6MQ Level 6 Unlocks] - Formular zum anfordern von Level 6 Unlocks ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3.5]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chit Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] 17886b73f431db628fa9aaa702644b2362b5ed58 0 98 701 700 2013-03-26T05:25:18Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best map editing practice]] c90a64ff4ca2c80c2b380f04a447bf43f8c97179 0 100 703 2013-04-15T03:11:48Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice]] babefc4250c41cd0fdb397db2c98a63bfe2cdcbd 0 99 702 2013-04-15T03:12:16Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice]] babefc4250c41cd0fdb397db2c98a63bfe2cdcbd 0 97 695 2013-04-15T03:12:42Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice]] babefc4250c41cd0fdb397db2c98a63bfe2cdcbd 10 39 11470 2013-04-15T03:31:54Z Kentsmith9 25 Created template wikitext text/x-wiki <div style="clear:both;"></div> 4b77d6ddcf09378cf4e7d9b70b8c921bdfa95a0d 11471 11470 2013-04-27T21:02:55Z Kentsmith9 25 Updated doc wikitext text/x-wiki <noinclude>'''Documentation:''' This template makes content wait until existing content (typically tables and images) is fully displayed in all columns before letting subsequent content be displayed. It uses the ''<nowiki><div style="clear:both;"></div></nowiki>'' formatting to prevent the extra line break that comes with ''<nowiki><br style="clear: both" /></nowiki>''. The following content after the line will appear on the actual page. ---- </noinclude><div style="clear:both;"></div> e696688e6243d751d6b582a2bef50cee5e170613 11472 11471 2013-04-27T21:21:47Z Kentsmith9 25 Modified to include left, right, or both wikitext text/x-wiki <noinclude>'''Documentation:''' This template makes content wait until existing content (typically tables and images) is fully displayed in all columns before letting subsequent content be displayed. It uses the ''<nowiki><div style="clear:TYPE;"></div></nowiki>'' formatting to prevent the extra line break that comes with ''<nowiki><br style="clear: both" /></nowiki>''. The TYPE variable is controlled with the second parameter as follows: * '''<nowiki>{{</nowiki>clear|left<nowiki>}}</nowiki>''' - Only the left column must be complete before subsequent content is displayed * '''<nowiki>{{</nowiki>clear|right<nowiki>}}</nowiki>''' - Only the right column must be complete before subsequent content is displayed * '''<nowiki>{{</nowiki>clear<nowiki>}}</nowiki>''' or '''<nowiki>{{</nowiki>clear|both<nowiki>}}</nowiki>''' - Both left and right columns must be complete before subsequent content is displayed The following content after the line will appear on the actual page. ---- </noinclude><div style="clear:{{{1|both}}};"></div> 7c4c629c670ef55f578458322afd1e9d389d3eb7 11473 11472 2013-04-28T03:39:12Z Kentsmith9 25 added template wikitext text/x-wiki <noinclude>'''Documentation:''' This template makes content wait until existing content (typically tables and images) is fully displayed in all columns before letting subsequent content be displayed. It uses the ''<nowiki><div style="clear:TYPE;"></div></nowiki>'' formatting to prevent the extra line break that comes with ''<nowiki><br style="clear: both" /></nowiki>''. The TYPE variable is controlled with the second parameter as follows: * '''<nowiki>{{</nowiki>clear|left<nowiki>}}</nowiki>''' - Only the left column must be complete before subsequent content is displayed * '''<nowiki>{{</nowiki>clear|right<nowiki>}}</nowiki>''' - Only the right column must be complete before subsequent content is displayed * '''<nowiki>{{</nowiki>clear<nowiki>}}</nowiki>''' or '''<nowiki>{{</nowiki>clear|both<nowiki>}}</nowiki>''' - Both left and right columns must be complete before subsequent content is displayed {{TemplateNotDisplayed}} </noinclude><div style="clear:{{{1|both}}};"></div> 445a6bc13c48a71eb4e6fe0d2db8eda4256ded0e 10 36 11456 11455 2013-04-15T04:11:05Z Kentsmith9 25 Trial 2 of anchor wikitext text/x-wiki <span id="{{{1|}}}"></span>}} 584a63d0e284d8e5e11238cba1eab88649b77638 11457 11456 2013-04-15T04:11:24Z Kentsmith9 25 fixed typo wikitext text/x-wiki <span id="{{{1|}}}"></span> 1789210ba11c3d9bbc7c46100223f86137328113 11458 11457 2013-04-28T00:24:09Z Kentsmith9 25 Documentation wikitext text/x-wiki <noinclude>'''Documentation:''' This template creates a point on a page that can be linked from other pages. Place the following example code on a page in the spot to which you need to link: '''<nowiki>{{</nowiki>anchor|Name for the link on the page<nowiki>}}</nowiki>''' Then from another page you can enter the code: '''<nowiki>[[</nowiki>PageNameWithNewAnchor#Name for the link on the page<nowiki>]]</nowiki>''' or if it is on the current page you can alternately use: '''<nowiki>[[</nowiki>#Name for the link on the page<nowiki>]]</nowiki>''' Note that both entries can also use the pipe (|) to display alternate text to the user instead of the actual link name. The following content after the line will appear on the actual page. ---- </noinclude><span id="{{{1|}}}"></span> cfcf94905f7f7b5572a46cc23cc11be8e46fd2dc 11459 11458 2013-04-28T03:35:46Z Kentsmith9 25 updated doc wikitext text/x-wiki <noinclude>'''Documentation:''' This template creates a point on a page that can be linked from other pages. Place the following example code on a page in the spot to which you need to link: '''<nowiki>{{</nowiki>anchor|Name for the link on the page<nowiki>}}</nowiki>''' Then from another page you can enter the code: '''<nowiki>[[</nowiki>PageNameWithNewAnchor#Name for the link on the page<nowiki>]]</nowiki>''' or if it is on the current page you can alternately use: '''<nowiki>[[</nowiki>#Name for the link on the page<nowiki>]]</nowiki>''' Note that both entries can also use the pipe (|) to display alternate text to the user instead of the actual link name. {{TemplateNotDisplayed}} </noinclude><span id="{{{1|}}}"></span> 43cab9e0255014b6c259c7234d44812025f755f2 0 96 603 602 2013-04-15T04:25:31Z Kentsmith9 25 /* When to Split a Two-Way Road (and when not to) */ added anchor wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the road segment properties tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] bf041b55cf06ce0b3d6681123979224c0f3ab19d 604 603 2013-04-26T00:09:01Z Kentsmith9 25 /* Toll roads */ wikilink to properties wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, select the segment(s), copy the [[permalink]] of that location, and post it in the [http://www.waze.com/forum/viewforum.php?f=265 Unlock request forum]. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] ca4fc13f39996fbe758e8d73240dbf5db995fc99 605 604 2013-05-10T04:50:15Z Kentsmith9 25 /* Locking Segments */ linked back to more details on unlocking wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. I wish I were kidding. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, refer to the page on [[Editing_ranks#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] ec6b1c8d4be57bc180704e4d3391ac6ed4e37905 611 610 2013-05-27T06:19:43Z Kentsmith9 25 /* How to "Un-Split" two One-Way Roads */ Embedded video wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === <!-- I came here yesterday to solve a UR that would clearly be solved if I ‘Un-Split’ the road since it passed all the conditions. However, after following these instructions I ended up missing addresses on the south side of the road and had to go back and add them one-by-one….ouch. After discovering what happened I found this discussion: http://www.waze.com/forum/viewtopic.php?f=8&t=48787&hilit=merge This discussion has videos from bgodette and step-by-step pictures from AlanOfTheBerg. As this wiki section stands right now, you will lose half of your addresses when you preform step #1 below of the Original steps. Here is a step that needs to be added to the new instructions: Since the above mentioned discussion is brand-new and active, I’m not going to change this section of the wiki below until all are in agreement. Original wiki instructions follow: --> <!-- Sorry to say it, but there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split but shouldn't have been--just look for the highest concentration of problem reports, and you'll find them!--you have some major map surgery ahead of you. Basically, for the length of the road, you're going to: # delete road segments on one side or the other*, including segments that connect the two sides; # remove all "orphaned" junctions; # change the direction of the preserved segments to two-way; # check/fix the connectivity of all the roads already connect to the side you kept; # connect (and set connectivity) of all the roads that used to be connected to the other side; # make sure all the new two-way segments are connected; and # adjust the geometry to move the two-way road segments to the middle of the road. '*' It usually saves time to preserve whichever side is already connected to more roads, so you may want to delete one side in some places, and the other side in other places. Just remember to re-connect them later. --> -------------- {{Red|Instructions being added now...}} The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers.’ # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you will notice the dashed line is attached to the dot on the street. # Select the dot and move it along the road closest to the entrance of the driveway to the building. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, refer to the page on [[Editing_ranks#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] afd1396e7922a841a92d2ed4355365fb0c9b9c8d 612 611 2013-05-27T06:49:04Z Kentsmith9 25 /* How to "Un-Split" two One-Way Roads */ Added new instructions wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from the this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # After reviewing the criteria for when to split or not split a road, if you cannot be sure which way to go, consider sending a [[permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=10 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that will delete the house address data on that part of the road. It would have to be manually looked up and added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment and for the entire length of the road you will need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and relalign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers.’ # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you will notice the dashed line is attached to the dot on the street. # Select the dot and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions; # Change the direction of the preserved segments to two-way; # Check/fix the connectivity of all the roads already connect to the side you kept; # Connect (and set connectivity) of all the roads that used to be connected to the other side; # Make sure all the new two-way segments are connected; and # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, refer to the page on [[Editing_ranks#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] d8f595a3c005164bfec7e9047bb8bd745fa8e6e6 10 68 249 248 2013-04-15T14:47:43Z Kentsmith9 25 Added glossary wikilink wikitext text/x-wiki ==Other Abbreviations== ''' ''Prefixes, directional abbreviations and other (non-suffix) abbreviations should not be used, except for state/ territory abbreviations & country abbreviations; under ISO 3166-1 alpha-3.'' ''' 1. Prefix abbreviations include: Mount (Mt.), and Saint (St.) Note: Mount (Mt.) is not the same as Mountain (Mtn.). :*Although they are common, can cause issues as variation and overlap exists between naming, usage, and prefix standards (I.e. What words to, and how to, abbreviate). :*Therefore a lake named "Lake Clair" would not be abbreviated, while if its documented name was "Clair Lake" it would be. 2. Directional abbreviations include: East (E), South West (SW), Central (CN), Upper (UP), and Lower (LR). :*In addition to not being abbreviated, directions should only be included when they are a part of the documented name, and not a suffix or prefix added at a later stage to describe location or orientation/ direction. 3. Other abbreviations include: Island (Is.), Quay (Qy), Reserve (Res) and Tunnel (Tunl). :*These are acceptable to be used when they are a suffix, but not acceptable when they are place names. :*Therefore "King-Tunnel Road" should have tunnel spelt in full, as it refers to a tunnel. While "Queen Tunnel-Road" could have tunnel abbreviated, as tunnel refers to the type of roadway, and is a part of the suffix. :*Likewise an Island named "Island Island" would be abbreviated to Island Is. 4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category. :*For example: California would be abbreviated to C.A. not CA and Victoria to VIC. :*Country abbreviations are done under "ISO 3166-1 alpha-3". Further information can be found on Wikipedia. ([http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 ISO 3166:]) :*Other regions include that of Suburbs, Districts, Localities, Shires and special purpose areas. (I.e. Indigenous, Military and Airport areas.) ==Standard Suffix Abbreviations== '''Notes:''' 1. Only abbreviate suffixes. :*"The Avenue", "The Green ", and etc. should not be abbreviated. :*"Circuit Avenue Road" would be abbreviated to Circuit Avenue Rd and not "Cct Ave Rd" :*A road named "Service way" should not be abbreviated, while "Pipeline Service way" should be. 2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens). 3. In the event that the original suffix is a plural (I.e contains a "s" at the end) and only its singular form is present as an abbreviation, simply add an "s" to the end of the abbreviation. Legend: # TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Untested |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mount|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pky|| Yes |- | Parkways||Pkys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Untested |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further Reading== === Forums === Please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: http://www.waze.com/forum/viewtopic.php?f=10&t=15178 === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. 2b39391823ee0c1a0df0cb1e93b311f63c92e982 1 107 710 2013-04-18T21:45:55Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#Parking_Lots]] 1530347befdd3b3565d9447ec640e15f0ff18f99 0 87 457 2013-04-22T20:49:56Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[At-Grade_Connectors]] d746335b6ee2d65935428fae2a42a993789f640a 0 78 416 415 2013-04-22T20:55:23Z Kentsmith9 25 /* Should the connector be mapped? */ Added Map Problem type wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|update requests]]) that the audible was too late, or that the map should have shown a connector *When you get an automated report ([[Map_Problems_in_Waze_Map_Editor|map problem]]) that the roads are too far apart due to the intersection being too far from the turn lane When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or Allow All Connections function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] 0e2d5bf8da4e4ed2ff0f5e265a371c9eb0eba0fe 0 86 455 2013-04-22T21:04:27Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[At-Grade_Connectors]] d746335b6ee2d65935428fae2a42a993789f640a 0 84 451 2013-04-22T21:04:59Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[At-Grade_Connectors]] d746335b6ee2d65935428fae2a42a993789f640a 0 85 453 2013-04-22T21:05:27Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[At-Grade_Connectors]] d746335b6ee2d65935428fae2a42a993789f640a 0 88 459 2013-04-22T21:09:43Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[At-Grade Connectors]] f5d61253324b84004e5e4429fef8c4919e28c89d 10 28 11341 11340 2013-04-25T02:12:39Z Kentsmith9 25 Sync with Template:CountriesList wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> [[Image:Ar.png]]&nbsp;[[Argentina]] [[Image:Au.png]]&nbsp;[[Australia]] [[Image:Be.png]] [[Belgium]] [[Image:Br.png]]&nbsp;[[Brasil]] [[Image:Ca.png]]&nbsp;[[Canada]] [[Image:Cn.png]]&nbsp;[[中国|中国 (China)]] [[Image:Co.png]]&nbsp;[[Colombia]] [[Image:Cr.png]]&nbsp;[[Costa Rica]] [[Image:Cz.png]]&nbsp;[[Czech]] [[Image:Cy.png]]&nbsp;[[Cyprus]] [[Image:Dk.png]]&nbsp;[[Denmark]] [[Image:De.png]]&nbsp;[[Deutsch|Deutschland]] [[Image:Ee.png]]&nbsp;[[Eesti]] [[Image:Es.png]]&nbsp;[[España]] [[Image:Fi.jpg]]&nbsp;[[Finland]] [[Image:Fr.png]]&nbsp;[[France]] [[Image:Ie.png]]&nbsp;[[Ireland]] [[Image:Il.png]]&nbsp;[http://www.waze.co.il ישראל] [[Image:India1.jpg]]&nbsp;[[India]] [[Image:In.png]]&nbsp;[[Indonesia]] [[Image:It.png]]&nbsp;[[Italy]] [[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan(日本)]] [[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] [[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] [[Image:Lux.gif]]&nbsp;[[Luxembourg|Lëtzebuerg]] [[Image:Hu.png]]&nbsp;[[Hungary|Magyarország]] [[Image:My.jpg]]&nbsp;[[Malaysia]] [[Image:Mx.gif|25px]]&nbsp;[[México]] [[Image:Nl.png]]&nbsp;[[Nederland]] [[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] [[Image:Oesterreich.png]]&nbsp;[[Österreich]] [[Image:Pl.png]]&nbsp;[[Poland]] [[Image:Pt.png]]&nbsp;[[Portugal]] [[Image:Ro.png]]&nbsp;[[Romania]] [[Image:Ru.png]]&nbsp;[[Russia]] [[Image:SRb.png]]&nbsp;[[Serbia]] [[Image:Sk.png]]&nbsp;[[Slovakia]] [[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] [[Image:Swiss1.png]]&nbsp;[[Switzerland]] [[Image:Se.png]]&nbsp;[[Sweden]] [[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] [[Image:Us.png]]&nbsp;[[USA]] ---- 61acb396997a328893647792b1a2555d74c30cdc 11342 11341 2013-04-25T02:13:29Z Kentsmith9 25 Sync with Template:CountriesList wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> [[Image:Ar.png]]&nbsp;[[Argentina]] [[Image:Au.png]]&nbsp;[[Australia]] [[Image:Be.png]] [[Belgium]] [[Image:Br.png]]&nbsp;[[Brasil]] [[Image:Ca.png]]&nbsp;[[Canada]] [[Image:Cn.png]]&nbsp;[[中国|中国 (China)]] [[Image:Co.png]]&nbsp;[[Colombia]] [[Image:Cr.png]]&nbsp;[[Costa Rica]] [[Image:Cz.png]]&nbsp;[[Czech]] [[Image:Cy.png]]&nbsp;[[Cyprus]] [[Image:Dk.png]]&nbsp;[[Denmark]] [[Image:De.png]]&nbsp;[[Deutsch|Deutschland]] [[Image:Ee.png]]&nbsp;[[Eesti]] [[Image:Es.png]]&nbsp;[[España]] [[Image:Fi.jpg]]&nbsp;[[Finland]] [[Image:Fr.png]]&nbsp;[[France]] [[Image:Ie.png]]&nbsp;[[Ireland]] [[Image:Il.png]]&nbsp;[http://www.waze.co.il ישראל (Israel)] [[Image:India1.jpg]]&nbsp;[[India]] [[Image:In.png]]&nbsp;[[Indonesia]] [[Image:It.png]]&nbsp;[[Italy]] [[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|日本 (Japan)]] [[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] [[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] [[Image:Lux.gif]]&nbsp;[[Luxembourg|Lëtzebuerg]] [[Image:Hu.png]]&nbsp;[[Hungary|Magyarország]] [[Image:My.jpg]]&nbsp;[[Malaysia]] [[Image:Mx.gif|25px]]&nbsp;[[México]] [[Image:Nl.png]]&nbsp;[[Nederland]] [[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] [[Image:Oesterreich.png]]&nbsp;[[Österreich]] [[Image:Pl.png]]&nbsp;[[Poland]] [[Image:Pt.png]]&nbsp;[[Portugal]] [[Image:Ro.png]]&nbsp;[[Romania]] [[Image:Ru.png]]&nbsp;[[Russia]] [[Image:SRb.png]]&nbsp;[[Serbia]] [[Image:Sk.png]]&nbsp;[[Slovakia]] [[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] [[Image:Swiss1.png]]&nbsp;[[Switzerland]] [[Image:Se.png]]&nbsp;[[Sweden]] [[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] [[Image:Us.png]]&nbsp;[[USA]] ---- e78b70dcef80173f23c629bcd2b722102a89ed9f 11343 11342 2013-04-25T06:10:54Z Kentsmith9 25 Sync with Template:CountriesList wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> [[Image:Ar.png]]&nbsp;[[Argentina]] [[Image:Au.png]]&nbsp;[[Australia]] [[Image:Be.png]] [[Belgium]] [[Image:Br.png]]&nbsp;[[Brasil]] [[Image:Ca.png]]&nbsp;[[Canada]] [[Image:Cn.png]]&nbsp;[[中国|中国 (China)]] [[Image:Co.png]]&nbsp;[[Colombia]] [[Image:Cr.png]]&nbsp;[[Costa Rica]] [[Image:Cy.png]]&nbsp;[[Cyprus]] [[Image:Cz.png]]&nbsp;[[Czech]] [[Image:Dk.png]]&nbsp;[[Denmark]] [[Image:De.png]]&nbsp;[[Deutsch|Deutschland]] [[Image:Ee.png]]&nbsp;[[Eesti]] [[Image:Es.png]]&nbsp;[[España]] [[Image:Fi.jpg]]&nbsp;[[Finland]] [[Image:Fr.png]]&nbsp;[[France]] [[Image:Ie.png]]&nbsp;[[Ireland]] [[Image:Il.png]]&nbsp;[http://www.waze.co.il ישראל (Israel)] [[Image:India1.jpg]]&nbsp;[[India]] [[Image:In.png]]&nbsp;[[Indonesia]] [[Image:It.png]]&nbsp;[[Italy]] [[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|日本 (Japan)]] [[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] [[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] [[Image:Lux.gif]]&nbsp;[[Luxembourg|Lëtzebuerg]] [[Image:Hu.png]]&nbsp;[[Hungary|Magyarország]] [[Image:My.jpg]]&nbsp;[[Malaysia]] [[Image:Mx.gif|25px]]&nbsp;[[México]] [[Image:Nl.png]]&nbsp;[[Nederland]] [[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] [[Image:Oesterreich.png]]&nbsp;[[Österreich]] [[Image:Pl.png]]&nbsp;[[Poland]] [[Image:Pt.png]]&nbsp;[[Portugal]] [[Image:Ro.png]]&nbsp;[[Romania]] [[Image:Ru.png]]&nbsp;[[Russia]] [[Image:SRb.png]]&nbsp;[[Serbia]] [[Image:Sk.png]]&nbsp;[[Slovakia]] [[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] [[Image:Se.png]]&nbsp;[[Sweden]] [[Image:Swiss1.png]]&nbsp;[[Switzerland]] [[Image:Ua.jpg]] [[Ukraine]] [[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] [[Image:Us.png]]&nbsp;[[USA]] ---- e62f8c6381b4c574a5c0b3db212c7c6943c1349d 10 66 11829 11828 2013-04-25T06:11:39Z Kentsmith9 25 Sync with Template:Countries wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutsch|Deutschland]] <li>[[Image:Ee.png]] [[Eesti]] <li>[[Image:Es.png]] [[España]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [http://www.waze.co.il ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai]] <li>[[Image:Hu.png]] [[Hungary|Magyarország]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand]] <li>[[Image:Oesterreich.png]] [[Österreich]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:Za.png]] [[South Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United_Kingdom|United Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul> 05a7fa5ec5a585e77bfbf1de22640ad4ff7609a7 11830 11829 2013-05-19T23:01:48Z Kentsmith9 25 Added English translations of countries not in English already wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutsch|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [http://www.waze.co.il ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul> 93fc0f3d25ff9927fe552c15c5893f34a93e5f26 0 71 280 279 2013-04-25T07:24:04Z Kentsmith9 25 fixed red wikitext text/x-wiki #REDIRECT [[Abbreviations & Acronyms]] 33ae33f6ce3f45e319f3f4e8f4c46f336b3ce3e6 10 51 162 2013-04-26T00:04:43Z Kentsmith9 25 created redirect wikitext text/x-wiki #REDIRECT [[Best_map_editing_practice#Toll_roads]] 7d679bd2966ee3e3a4422260b611b2d8692bcec1 164 163 2013-05-10T03:04:47Z Kentsmith9 25 Converted to DAB wikitext text/x-wiki '''Toll''' may refer to: * [[Best_map_editing_practice#Toll roads|Toll roads]], the best map editing practice for this setting * [[Creating_and_Editing_street_segments#Toll road|Toll road]], the setting in the Waze Map Editor * [[Avoid toll roads]], the setting in the Waze client app to route without using toll roads {{Disambig}} 5060d09e327a8bbeff09bc8a320711c9a20052a4 165 164 2013-05-10T04:33:30Z Kentsmith9 25 wording adjustment wikitext text/x-wiki '''Toll''' may refer to: * [[Best_map_editing_practice#Toll roads|Toll roads]], the best map editing practice for when to create them * [[Creating_and_Editing_street_segments#Toll road|Toll road]], the check box in the Waze Map Editor * [[Avoid toll roads]], the setting in the Waze client app to route without using toll roads {{Disambig}} 00c7ead9cbf5aa54681221b2a0a2b1ca27066617 10 52 11625 2013-04-26T05:47:56Z Kentsmith9 25 Created template wikitext text/x-wiki <span style="color:#FF0000">{{{1}}}</span> b1315688cac57c8c5fda5a8a666e4c96519ba118 11626 11625 2013-04-28T05:04:05Z Kentsmith9 25 Added doc wikitext text/x-wiki <noinclude>'''Documentation:''' This template displays the text after the pipe (|) in red using the wiki markup: '''<nowiki><span style="color:#FF0000">{{{1|}}}</span></nowiki>''' {{TemplateDisplay}} <span style="color:#FF0000">This is an example of text passed as the second parameter of this template.</span> </noinclude><span style="color:#FF0000">{{{1|}}}</span> a9173306b46bcfdd77078a3b2956d75bff59e8a1 0 25 11243 11242 2013-04-26T08:10:03Z Kentsmith9 25 Removed obsolete link; better link already present wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] == '''Waze und was nun?''' == Nach der [[How to get the free Waze client|Installation]] von Waze hast du sicher ein paar Fragen. * Bitte wahre den Anstand im [[Diskussionsforum|Forum]]. * Alles was schon gesagt wurde findest du über die [http://www.waze.com/forum/search.php Foren Suche]. * Sehe im [[Main Page|Wiki]] nach. Länderspezifische Wikis sind ebenfalls vorhanden. * Lies die Seite über [[Häufig gestellte Fragen|Häufig gestellte Fragen]] oder die [[Known issues|Seite]] über bereits bekannte [[Problems and Issues|Probleme]]. * Wenn du einen Post schreibst, verwende einen angemessenen Titel. Grossschrift und Sonderzeichen sind nicht nötig! * Gebräuchliche Begriffe findest Du im [[Glossar]] * Falls es sich um Fragen des [[Client device|Clients]] resp. der Waze Applikation auf deinem Smartphone handelt, vergiss nicht Daten wie: Verwendetes Smartphone, OS inkl. Version und installierte Waze Version zu erwähnen. <br>Man darf diese Daten auch in die eigene Signatur packen: <br>''User Control Panel -> Profile -> Edit Signature'' * Lese die [[User Manual|Anleitung]] zu deinem Smartphone. * Gib bitte an in welchem Land du mit Waze unterwegs bist, so erübrigt sich die Frage auf welchem [[Die Server Bänke|Server]] du dich befindest:<br>''User Control Panel -> Profile, unter Location.'' * Schau die [[Mein Dashboard|Dashboard]] Seite an bevor du dazu eine Frage stellst. * Das Wiki mag an manchen Stellen nicht mehr Zeitgemäss sein, daher steht es dir frei als erfahrener Wazer mitzuhelfen das Wiki zu [[Update this Wiki|aktualisieren]]. * Der Waze Staff ist nicht gross, die meisten Antworten erhältst du von anderen Wazern im Forum. Deshalb ist es wichtig, dass du dich an die oben erwähnten Vorschläge hältst. Es sind sonst nicht allzu viele Antworten zu erwarten. <br>Denn nach dem zwanzigsten Post mit Titeln wie: [[Ablauf der Aktualisierungsprozesse|"Meine Punkte oder Map-Edits wurden nicht aktualisiert"]] oder [http://www.waze.com/forum/search.php "Wieso sieht man keine Eisenbahnen"], wird nicht jeder gewillt sein zu antworten. * Du darfst natürlich auch [[Make suggestions to improve Waze|Vorschläge]] machen um Waze zu verbessern. <br> Wenn du dir nicht selbst helfen konntest, frage im Forum nach. <br> Wenn alles fehl schlägt und man dir im Forum nicht helfen konnte, verwende als erstes die [http://www.waze.com/support/ Quick Help] der Supportseite. Oder melde dich per [[Mail an den Support|Mail]] an Waze. <br>'''Weitere Informationen:''' * Warum sagt Waze im [[How to create a roundabout|Kreisverkehr]] "Die erste Ausfahrt nehmen" oder "Rechts abbiegen?" * Warum sagt Waze beim [[How Waze determines turn / keep / exit maneuvers|Abbiegen]] "Rechts halten" oder "Rechts Abbiegen"? * Was is ein [[Area Manager|Area Manager]]? * Teile deine [https://docs.google.com/spreadsheet/ccc?key=0AnK4ogNrUnhmdDM1LXIzNXNFblJMMkJRelo0NzR5dkE&hl=en_GB#gid=1 Kontakt Informationen] mit anderen AM und der Community. * Wie lauten die Adressen der [[RSS Feeds|RSS Feeds]] für Waze? <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] c3923faede5390a5a2a13348b3a42a15147ed6ef 10 58 182 2013-04-27T18:50:19Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Map_Editor_Interface_and_Controls#Zoom_Control]] f8a73a3d5a9552fa9e09f83b9661bfd78dabec77 183 182 2013-05-03T07:39:07Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Zoom''' may refer to: * [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom control]], the interface in the WME to set the visual zoom of the map. * [[Zoom#Scale|Zoom scale]] or zoom level, the meter or feet measurement associated in WME * [[Auto zoom|Auto zoom]], controls the map resolution in the Waze application {{Disambig}} 81f96db3885c3b1e8950e9b72dfebdd94b7f0d85 184 183 2013-05-03T07:57:11Z Kentsmith9 25 Added app zoom wikitext text/x-wiki '''Zoom''' may refer to: * [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom control]], the interface in the WME to set the visual zoom of the map * [[Zoom#Scale|Zoom scale]] or zoom level, the meter or feet measurement associated in WME * [[Auto zoom|Auto zoom]], automatically controls the map resolution in the Waze application * [[Zoom control (app)|Zoom control]], manually sets the map resolution in the Waze application {{Disambig}} 1b9cc84ade6e1e88db883ca9346328271c73daa4 185 184 2013-05-03T07:57:51Z Kentsmith9 25 fixed wikilink wikitext text/x-wiki '''Zoom''' may refer to: * [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom control]], the interface in the WME to set the visual zoom of the map * [[Zoom#Scale|Zoom scale]] or zoom level, the meter or feet measurement associated in WME * [[Auto zoom|Auto zoom]], automatically controls the map resolution in the Waze application * [[Zoom control (app)|Zoom control (app)]], manually sets the map resolution in the Waze application {{Disambig}} bf70493599a0bee08e62462a52a982d5e030a9ef 186 185 2013-05-06T02:20:37Z Kentsmith9 25 Fixed DAB wikitext text/x-wiki '''Zoom''' may refer to: * [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom control]], the interface in the WME to set the visual zoom of the map * [[Map_Editor_Interface_and_Controls#Scale|Zoom scale]] or zoom level, the meter or feet measurement associated in WME * [[Auto zoom|Auto zoom]], automatically controls the map resolution in the Waze application * [[Zoom control (app)|Zoom control (app)]], manually sets the map resolution in the Waze application {{Disambig}} 2f2bcb05deca08261a4358c3790d5cb069c7b7e6 0 27 76 75 2013-05-10T03:29:26Z Kentsmith9 25 Added "lock level" wikitext text/x-wiki '''Level''' may refer to: * [[Creating_and_Editing_street_segments#Road_Level|Road Level]], the relative altitude of the road compared to other roads nearby * [[Lock level]], the security setting on roads preventing alteration by editors below the road's level * Editing Level, [[Points#Map_editing_rank|Map Editing Rank]] relative to other editors * Zoom Level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] {{Disambig}} 6492283ece391a22016eefb0cb2d79288e4dd191 77 76 2013-05-10T03:33:19Z Kentsmith9 25 fixed wikilink wikitext text/x-wiki '''Level''' may refer to: * [[Creating_and_Editing_street_segments#Road_Level|Road Level]], the relative altitude of the road compared to other roads nearby * Lock level, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's level * Editing Level, [[Points#Map_editing_rank|Map Editing Rank]] relative to other editors * Zoom Level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] {{Disambig}} 252049eec05ff3fd6183285611d9f5f30d01469c 0 30 90 89 2013-05-10T04:25:56Z Kentsmith9 25 Converted to DAB wikitext text/x-wiki '''Lock''' may refer to: * [[Best map editing practice#Locking Segments|Locking segments]], the best map editing practice * [[FAQ#What_is_a_locked_road.3F|Locked road]], how it works and what it does * Lock level, setting the security level of a road in the Waze Map Editor [[Map_Editor_Interface_and_Controls#General_Tab|General tab]] * Lock (Landmark), setting on Waze Map Editor when editing a [[Map_Editor_Interface_and_Controls#Tabs_when_a_landmark_is_selected|landmark]] {{Disambig}} 0b8bdcb56909d2986c8ab291a16b95946f1a9eb4 91 90 2013-05-10T04:57:50Z Kentsmith9 25 improved wikilink wikitext text/x-wiki '''Lock''' may refer to: * [[Editing_ranks#Locked_segments|Locked segments]], how they work and how to unlock them * [[Best map editing practice#Locking Segments|Locking segments]], the best map editing practice * Lock level, setting the security level of a road in the Waze Map Editor [[Map_Editor_Interface_and_Controls#General_Tab|General tab]] * Lock (Landmark), setting on Waze Map Editor when [[Map_Editor_Interface_and_Controls#Tabs_when_a_landmark_is_selected|editing a landmark]] {{Disambig}} Editing_ranks#Locked_segments d1e7a96cf83df62ab695cc5bf92fdb1e581eb659 92 91 2013-05-10T04:58:08Z Kentsmith9 25 fixed typo wikitext text/x-wiki '''Lock''' may refer to: * [[Editing_ranks#Locked_segments|Locked segments]], how they work and how to unlock them * [[Best map editing practice#Locking Segments|Locking segments]], the best map editing practice * Lock level, setting the security level of a road in the Waze Map Editor [[Map_Editor_Interface_and_Controls#General_Tab|General tab]] * Lock (Landmark), setting on Waze Map Editor when [[Map_Editor_Interface_and_Controls#Tabs_when_a_landmark_is_selected|editing a landmark]] {{Disambig}} 9f3d43838e6e56800188403113a6cfe5e2eaf0ec 0 32 99 2013-05-19T17:11:31Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Map updates''' may refer to: * Map updates, the total points a Waze editor has displayed on their [[Dashboard#Your_Rank_and_Points|Dashboard]] * Map updates, related to the FAQ question [[FAQ#When_do_my_edits_show_up_in_the_Waze_app.3F|When do my edits show up in the Waze app]] * Map updates, how often the servers are updated through the [[timeline of updating process]] It may also refer to: * [[Update Requests in Waze Map Editor]], the balloon icons from user reported map problems * [[Map Problems in Waze Map Editor]], the balloon icons from automated system reports {{Disambig}} 07c83629fbb3dbbdf2c5edc6ac28f0543b7296df 100 99 2013-05-19T17:49:42Z Kentsmith9 25 Added WME wikitext text/x-wiki '''Map updates''' may refer to: * Map updates, the total points a Waze editor has displayed on their [[Dashboard#Your_Rank_and_Points|Dashboard]] * Map updates, related to the FAQ question [[FAQ#When_do_my_edits_show_up_in_the_Waze_app.3F|When do my edits show up in the Waze app]] * Map updates, how often the servers are updated through the [[timeline of updating process]] * Map updates, made by users through the [[Waze Map Editor]] It may also refer to: * [[Update Requests in Waze Map Editor]], the balloon icons from user reported map problems * [[Map Problems in Waze Map Editor]], the balloon icons from automated system reports {{Disambig}} 4bed646857c26bcf30dc413c81f177bba4f41634 0 33 103 2013-05-19T17:47:14Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Map_updates]] a655ea7720d219ccf798900b0b5d736d8a532166 0 2 2 2013-07-23T20:24:35Z Kentsmith9 25 Created disambiguation wikitext text/x-wiki '''Address''' may refer to: * Address, used to look up and edit [[House_Numbers_in_WME|house numbers]] * [[Creating_and_Editing_street_segments#Address_Properties|Address properties]], identifying the country, state, city, and road name of a segment {{Disambig}} ec10ef9a621de370008af0dd316107fc1ab38657 0 80 444 2013-07-26T02:33:36Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[At-Grade_Connectors]] d746335b6ee2d65935428fae2a42a993789f640a 0 81 446 2013-07-26T02:34:00Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[At-Grade_Connectors]] d746335b6ee2d65935428fae2a42a993789f640a 10 52 11627 11626 2013-08-02T03:17:35Z Kentsmith9 25 Fixed template that somehow got transcluded wikitext text/x-wiki <noinclude>'''Documentation:''' This template displays the text after the pipe (|) in red using the wiki markup: '''<nowiki>{{Red|Display this in red.}}</nowiki>''' {{TemplateDisplay}} {{Red|This is an example of text passed as the second parameter of this template.}} </noinclude><span style="color:#FF0000">{{{1|}}}</span> 5c28b0786db4aa61a35873da4abc5dd00498997d 11628 11627 2013-08-02T03:22:43Z Kentsmith9 25 Undo revision 41029 by [[Special:Contributions/Kentsmith9|Kentsmith9]] ([[User talk:Kentsmith9|talk]]) Repaired my repair wikitext text/x-wiki <noinclude>'''Documentation:''' This template displays the text after the pipe (|) in red using the wiki markup: '''<nowiki>{{Red|This text will display in red.}}</nowiki>''' {{TemplateDisplay}} <span style="color:#FF0000">This is an example of text passed as the second parameter of this template.</span> </noinclude><span style="color:#FF0000">{{{1|}}}</span> 99f93633d2e4e44c8b455f2f0636a933eac97636 11629 11628 2013-08-02T03:24:59Z Kentsmith9 25 Undo revision 41030 by [[Special:Contributions/Kentsmith9|Kentsmith9]] ([[User talk:Kentsmith9|talk]]) An edit war with myself :-) wikitext text/x-wiki <noinclude>'''Documentation:''' This template displays the text after the pipe (|) in red using the wiki markup: '''<nowiki>{{Red|Display this in red.}}</nowiki>''' {{TemplateDisplay}} {{Red|This is an example of text passed as the second parameter of this template.}} </noinclude><span style="color:#FF0000">{{{1|}}}</span> 5c28b0786db4aa61a35873da4abc5dd00498997d 11630 11629 2014-02-03T02:56:56Z Kentsmith9 25 Moved doc to separate page wikitext text/x-wiki <span style="color:#FF0000">{{{1|}}}</span><noinclude>{{doc}}</noinclude> f75c559fc96e089c2981bc3ffd651fd873827dca 0 29 86 2013-08-02T04:34:44Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[Level]] c720e914a1ce10cf7929073e205e071c850de911 0 24 68 67 2013-08-04T22:41:25Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Junction''' may refer to: * Glossary entry for [[Glossary#Junction_or_Junction_Point|Junction]] with definition and images * [[Junction Style Guide]], detailed coverage of different junction types * [[Creating_and_Editing_street_segments#Junctions|Junction]], moving and removal/merging instructions {{Disambig}} 66b219db424f6098c55388ba5abbe88d766af424 0 16 36 2013-08-04T22:47:15Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Errors''' may refer to: * [[WME errors]], those seen in the Waze Map Editor application * Errors automatically reported by Waze servers and displayed as [[Map_Problems_in_Waze_Map_Editor|map problems in WME]] * Errors reported by Waze application users and displayed as [[Update_Requests_in_Waze_Map_Editor|update requests in WME]] {{Disambig}} a4cebfbf958b2c616c20b32cff79def915b1cb47 10 36 11460 11459 2013-09-12T02:03:30Z Kentsmith9 25 Cap change wikitext text/x-wiki <noinclude>'''Documentation:''' This template creates a point on a page that can be linked from other pages. Place the following example code on a page in the spot to which you need to link: '''<nowiki>{{</nowiki>Anchor|Name for the link on the page<nowiki>}}</nowiki>''' Then from another page you can enter the code: '''<nowiki>[[</nowiki>PageNameWithNewAnchor#Name for the link on the page<nowiki>]]</nowiki>''' or if it is on the current page you can alternately use: '''<nowiki>[[</nowiki>#Name for the link on the page<nowiki>]]</nowiki>''' Note that both entries can also use the pipe (|) to display alternate text to the user instead of the actual link name. {{TemplateNotDisplayed}} </noinclude><span id="{{{1|}}}"></span> a114fb21a0b5bb1d5fd837ab4877b513c2197f3d 11461 11460 2014-02-02T20:31:24Z Kentsmith9 25 Moved documentation to separate page wikitext text/x-wiki <span id="{{{1|}}}"></span><noinclude>{{doc}}</noinclude> cfec2c1b18568a30739086d9b5ec285912596cb2 112 2014-02-03T18:07:15Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki {{NeedPage}} It should be a disambiguation page linking to: Park landmarks Parking landmarks Parking icons Finding Parking lots 35c70e4b158be50db8666829d151b35055abfec0 113 112 2014-02-03T18:09:11Z Kentsmith9 25 fixed formatting wikitext text/x-wiki {{NeedPage}} {{red|It should be a disambiguation page linking to: Park landmarks, Parking landmarks, Parking icons, and Finding Parking lots}} 911c567b51de25e8b01d0eb276d6f34d21d7d43c 0 4 8 2013-09-16T18:50:40Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[FAQ#What_do_I_do_when_Waze_has_my_destination_or_address_at_the_wrong_location.3F]] 45d84e8a072a050ce54afbf84b0e560e019b3527 10 41 134 2013-09-29T16:29:48Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Restriction''' may refer to: * [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|Turn restrictions]], controlling turns 100% of the time * [[Scheduled restrictions]], controlling traffic flow (turns and segments) for some or all vehicle types * Editing restrictions, controlled by a user's [[Editing ranks|editing rank]] {{Disambig}} 9891e8bef529dabe886ddf5af46e5eb2bfc1e464 0 27 78 77 2013-10-17T06:04:57Z Kentsmith9 25 Fixed level vs rank reference wikitext text/x-wiki '''Level''' may refer to: * [[Creating_and_Editing_street_segments#Road_Level|Road Level]], the relative altitude of the road compared to other roads nearby * Zoom Level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] * Lock level, is actually lock rank, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's rank * Editing Level, is actually [[Points#Map_editing_rank|Map Editing Rank]] relative to other editors {{Disambig}} bb0ba775cf88ee736562ff3b2e558cce2670f33f 79 78 2013-12-15T06:45:49Z Kentsmith9 25 corrected like from road level to road elevation wikitext text/x-wiki '''Level''' may refer to: * Road level, the relative [[Creating_and_Editing_street_segments#Road_elevation|elevation]] of the road compared to other roads nearby * Zoom level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] * Lock level, is actually lock rank, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's rank * Editing level, is actually [[Points#Map_editing_rank|Map Editing Rank]] relative to other editors {{Disambig}} fa85be48035c05329bf19fe2c6bedddf6cd7d608 80 79 2014-02-01T03:49:56Z Kentsmith9 25 fixed road level wikitext text/x-wiki '''Level''' may refer to: * Road level, is actually [[Creating_and_Editing_street_segments#Road_elevation|road elevation]], relative to other roads nearby * Zoom level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] * Lock level, is actually lock rank, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's rank * Editing level, is actually [[Points#Map_editing_rank|Map Editing Rank]] relative to other editors {{Disambig}} 8b596ca43513875bbc59c86077228f04f50bf709 81 80 2014-02-01T04:11:51Z Kentsmith9 25 Fixed bad links wikitext text/x-wiki '''Level''' may refer to: * Road level, is actually [[Creating_and_Editing_street_segments#Road_elevation|road elevation]], relative to other roads nearby * Zoom level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] * Lock level, is actually lock rank, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's rank * Editing level, is actually [[Your_Rank_and_Points#Map_editing_rank|Map Editing Rank]] relative to other editors {{Disambig}} e5b8034e845c8eb23be586ddfd7a39f3998c6653 0 96 617 616 2013-10-18T14:00:57Z Kentsmith9 25 Fixed permalinks wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that will delete the house address data on that part of the road. It would have to be manually looked up and added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment and for the entire length of the road you will need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and relalign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers.’ # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you will notice the dashed line is attached to the dot on the street. # Select the dot and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions; # Change the direction of the preserved segments to two-way; # Check/fix the connectivity of all the roads already connect to the side you kept; # Connect (and set connectivity) of all the roads that used to be connected to the other side; # Make sure all the new two-way segments are connected; and # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Recent experience has changed my thinking regarding road levels. Given the current editor limitations, I have found that it is more important to know that road level is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent level across multiple segments of the same road. I use level 0 as a "sentinel value" that signifies that a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at level 0, set it to a non-zero value that reflects its relative level. If both levels are already non-zero, either they are already correct--in which case no further action is required--or they are incorrect, in which case the area needs to be studied carefully, so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting one segment's level, or perhaps several segments will need to be adjusted. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Or perhaps take a course in Topology at your local community college. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different levels as needed--and hope nobody deletes that "unnecessary" junction without investigating why it might be there. (In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.) ==== Caveat re. Levels ==== No matter what levels road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the levels of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_Level|Road Levels]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their level increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their levels are correct, and then re-connect them. Note that Railroad crossings at the level of a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should only be used on high-value roads and complicated junctions to prevent inexperienced lower level editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing level than you, refer to the page on [[Editing_ranks#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot *it allows the Waze client to get off the main road, avoidiing erroneous traffic reports ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. Waze has changed the way that Parking Lot roads route as of June 2012. Parking Lot roads now have a transition penalty when transitioning from the Parking Lot road to another road type. This penalty decreases the chance that Waze will route through a Parking Lot as a shortcut but allow better navigation in and out of the Parking Lot. Every segment that is used to map a Parking Lot should be of the Parking Lot segment type. It is no longer advisable to mix road types within the Parking Lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 06728a21e646c519037c2f2c895f699791210a65 629 628 2013-12-28T19:01:34Z Kentsmith9 25 /* Overpasses & Underpasses */ Removed editor's opinion and converted to general guidance. wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that will delete the house address data on that part of the road. It would have to be manually looked up and added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment and for the entire length of the road you will need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and relalign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers.’ # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you will notice the dashed line is attached to the dot on the street. # Select the dot and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions; # Change the direction of the preserved segments to two-way; # Check/fix the connectivity of all the roads already connect to the side you kept; # Connect (and set connectivity) of all the roads that used to be connected to the other side; # Make sure all the new two-way segments are connected; and # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment *there is no way to drive on that segment without eventually paying a toll (such as at an exit) In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_ranks#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a transition penalty when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 933b1a1cbe8f1b9d8f73d68b1cd8744fc02275cd 630 629 2013-12-28T19:06:22Z Kentsmith9 25 /* Toll roads */ Clarified not marking any segments before the actual toll wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers & others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first & foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split if:''' * GPS tracks show a clearly definable gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-Turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that will delete the house address data on that part of the road. It would have to be manually looked up and added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment and for the entire length of the road you will need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and relalign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers.’ # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you will notice the dashed line is attached to the dot on the street. # Select the dot and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions; # Change the direction of the preserved segments to two-way; # Check/fix the connectivity of all the roads already connect to the side you kept; # Connect (and set connectivity) of all the roads that used to be connected to the other side; # Make sure all the new two-way segments are connected; and # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done--but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names will be lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Since limited-access roads--typically Freeways & Major Highways--offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered & exited solely by ramps. Such roads almost always should be mapped as separate one-way segments--and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Ramps should always be locked to preserve directionality, since they often run especially close to other ramps that flow in the opposite direction. (Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses & Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you will run into a situation in which no set of values will work. For example, three segments named A, B and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it will help (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" will give routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It will not prevent Waze from snapping a driver to the segments, if it determines they are on such a lane, and any recalculation of the route from these segments will then be correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed * Entrances and exits to the HOT lanes are limited to help maintain high speeds * There are no entrance/exit combinations where the toll fare rules don't apply * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes", however the term "Express Lanes" is also used by various regional governments for non-HOT lanes. For Waze purposes, a road needs to meet all the above listed criteria to be considered a HOT lane. The entrances to HOT lanes should be marked with the toll flag. This will prevent Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Since Waze does not currently support HOV lanes, HOV users with toll avoidance turned on will not be routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes will need to navigate themselves to the HOT lanes, they will not be routed onto them by the Waze client. As with standard HOV lanes, HOV users will need to recalculate the route for Waze to snap them to the HOT lane. Since HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_ranks#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] will provide the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time & expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into & out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it will be necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a transition penalty when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which will go out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they will need to be edited as above before they will become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings will have [[classification_of_crossings|standard ways to handle them]] [[Waze Map Editor|Back to Editing Manual]] 520e5690728f991af8ab27926df7e87f8d1d8cea 0 1 4808 1 2013-11-04T15:45:38Z Kentsmith9 25 Added user maintained template wikitext text/x-wiki {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{Technical}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} 84fec5a28cd0a991712d6b3ae126ab2c0623b8ea 4809 1 2013-11-05T06:03:16Z Kentsmith9 25 Added user maintained template wikitext text/x-wiki {{Template:UserMaintainedTop}} {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{Technical}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} d89b5ee3daefaf558eeda7b5e84091fc4f03b7aa 4815 1 2014-02-03T00:02:39Z Kentsmith9 25 Reverted edits by [[Special:Contributions/Issamxml|Issamxml]] ([[User talk:Issamxml|talk]]) to last revision by [[User:AndyPoms|AndyPoms]] wikitext text/x-wiki {{Template:UserMaintainedTop}} {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{Technical}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} d89b5ee3daefaf558eeda7b5e84091fc4f03b7aa 0 5 10 2013-11-05T07:14:57Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[House_Numbers_in_WME]] aeb096831979e74d7d0acf56a22658cbe79992d8 10359 10358 2013-12-04T09:23:11Z Popel22 24 /* Hauptziele */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Einleitung== Wie Waze selbst ist diese Seite durch die Gemeinschaft entstanden und entwickelt sich kontinuierlich weiter. Viele hilfreiche Seiten existieren bereits unter [[Der Area Manager]], wie man den [[Der Waze Map-Editor| Karteneditor]] benutzt, Kartenfehler identifiziert und bearbeitet, Standards um Straßen zu klassifizieren und zu benennen und eine Seite über [[Häufig gestellte Fragen]]. Der Zweck dieser Seite ist es, Area-Managern und allen Benutzern zu helfen, eine Karte zu erstellen, welche für alle Waze-Endbenutzer während der Fahrt gut funktioniert. Auch kann so Mehraufwand durch nochmaliges Bearbeiten auf Grund von Fehlern oder Beschränkungen der Waze-Applikation vermieden werden. Feedback zur Übersetzung oder Vorschläge bitte per [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] ==Anleitungen== Im Wiki finden sich zahlreiche Anleitungen. Das Wichtigste am Anfang ist daher, sich mit den Anleitungen auseinanderzusetzen. Also lies die [[Anleitung zum Bearbeiten der Karte]] sorgfältig, bevor Du die Karte bearbeitest. ==Hauptziele== ===Benutzerfreundlichkeit=== Wenn es um die Karte geht, ist das oberste Gebot: Für den Waze-Benutzer eine einfache Karte zu erstellen, der einfach zu folgen ist auf dem kleinen Bildschirm. Die Anweisungen sollen klar und sinnvoll sein und nur dann erscheinen, wenn sie auch gebraucht werden. ===Einfachheit=== Es soll nicht jede einzelne Spur auf der Karte eingezeichnet werden. Dies führt häufig nur zu unnötiger Komplexität, unlogischen Anweisungen beim Navigieren sowie unübersichtlichen Verhältnissen auf der Karte und schlussendlich zu unnötiger Mehrarbeit beim Korrigieren. ===Erhaltung des bestehenden Zustandes=== Durch das Befahren der Straßen werden in den Segmenten Informationen gespeichert, wie z.B. die Geschwindigkeit, welche für das optimale Routing benötigt wird. Wenn ein Segment gelöscht wird, gehen diese Informationen verloren. Wenn an einem unübersichtlichen Gewirr von Segmenten gearbeitet wird, ist es die bessere Wahl, diese weiterzuverwenden, anstatt bestehende zu löschen und neu zu zeichnen. ==In der Praxis== ===In zwei Einbahnstraßen aufteilen oder nicht?=== Es ist selten eine gute Idee, eine Straße, die nur durch Ein- und Ausfahrten auf eine Autobahn oder Hauptverkehrsstraße verbunden ist, in zwei Einbahnen aufzuteilen. An einer Kreuzung müssen auch nicht die Einmündungen aufgeteilt werden. Kreuzungen werden dadurch unnötig kompliziert, auf dem Bildschirm ist nichts mehr richtig zu erkennen, und die Anweisungen bei der Navigation sind verwirrend oder unsinnig. <br> <b>Eine Straße sollte in zwei Einbahnen aufgeteilt werden wenn:</b> * Mindestens 5 Meter Abstand zwischen den Fahrspuren besteht. (Abgetrennt durch Beton, Blumentöpfe oder Beete, Bäume oder Grasflächen.) * Die GPS-Punkte liegen bei einem Zoomlevel von 100 Metern im Karteneditor genügend weit auseinander. <br> <b>Eine Straße sollte nicht in zwei Einbahnen aufgeteilt werden wenn:</b> * Eine nicht befahrbare Fläche von weniger als 5 Metern zwischen den Fahrspuren besteht. * Eine längere Abbiegespur zwischen beiden Fahrtrichtungen existiert. * Viele Straßen kreuzen, die nur auf die nächstliegende Fahrbahn führen. * Google Maps oder andere Karten die Straßen so anzeigen. ===Wie man zwei Einbahnen zu einer Fahrspur vereint=== Wer eine Straße in zwei Fahrspuren aufteilt, sollte auch verstehen, was alles dazugehört, dies rückgängig zu machen. Es gibt leider keinen einfachen Weg zwei getrennte Fahrspuren wieder in eine zweispurige Straße zurückzuwandeln. Deshalb sollte man sich das Aufteilen gut überlegen. Wenn man eine Straße antrifft, die nicht aufgeteilt sein sollte, erkennt man dies sehr gut an der Summe der Fehlermeldungen der User. Dort wo die meisten Meldungen liegen brennt es in der Regel. Danach beginnt die hohe Kunst der Karten-Chirurgie am Waze-Karteneditor. Folgende Schritte sind zu erledigen: # Löschen der einen oder anderen Seite inkl. der Segmente, die beide Straßen verbinden. # Alle verwaisten Kreuzungen entfernen. # Richtungsänderungen an der verbleibenden Straße vornehmen. # Alle Abbiegeverbote kontrollieren. # Verbinden inkl. Abbiegeverbote aller Straßen, die in die verbleibende Straße münden. # Sicherstellen, dass die verleibende Straße korrekt in beide Richtungen verbunden ist. # Die Geometrie der zweispurigen Straße in die Mitte korrigieren. Damit man sich damit nicht zu viel Arbeit einheimst, sollte man vorher die richtige Straße auswählen, die verbleiben soll. Dies entscheidet man natürlich anhand der bereits verbundenen Segmente. Man kann auch übers Kreuz löschen damit man schneller vorwärts kommt. Nicht vergessen die verbleibende Straße wieder korrekt mit ihr selbst zu verbinden. ===Autobahnen und Anschlüsse=== Langstrecken-Navigation ist nicht möglich, wenn die Autobahnen nicht korrekt verbunden sind. Deshalb ist diesem Thema besondere Aufmerksamkeit zu widmen. Man kann sehr viel bewirken, wenn man diese korrekt erstellt. Besondere Überlegungen müssen bei eingeschränkt befahrbaren Straßen angestellt werden. Es kann bei unsorgfältiger Vorgehensweise auch mehr Schaden enstehen, als an normalen Quartierstraßen. ==== Straßen ==== Beschränkt zugängliche Straßen mit mehreren Spuren in beiden Richtungen, die durch ein Hindernis zwischen den Spuren abgetrennt sind und allein durch Rampen zugänglich sind, sollten fast immer in zwei Einbahnen aufgeteilt werden. Andere normale Straßen sollten meistens nicht aufgeteilt werden. ==== Ein- und Ausfahrten ==== Einfahrten sollten nach der Richtung in die sie führen benannt werden. Ausfahrten sollten nach der Ausfahrtnummer - wenn vorhanden - und auch der Beschilderung der Ausfahrten benannt werden. Ein- und Ausfahrten sollten immer auf “Gesperrt“ gesetzt werden, um die Richtung zu erhalten, da viele auch eine naheliegende entgegengesetzte Spur besitzen. Werden solche Segmente nicht gesperrt, wird man früher oder später das Ganze nochmal bearbeiten müssen, wenn sich die Richtung einer Ein- oder Ausfahrt geändert hat. Dabei auch gleich die Verbindungen und Abbiegeverbote kontrollieren, bevor Segmente gesperrt werden. * Es gibt in den länderspezifischen Wikis mehr Informationen zur Benennung. * Verstehe den Unterschied zwischen Ein- und Ausfahrten und ebenerdigen [[Abbiegespuren]] ==== Über- und Unterführungen ==== Erfahrungen haben gezeigt, dass es sinvoller ist einzelnen bestimmten Segmenten einen unterschiedlichen Level zu geben, als längeren Straßen die nicht durch Kreuzungen unterteilt sind. Autobahnen beispielsweise sollten generell auf Level 0 bleiben. Brücken die darüber führen Level 1. Über- oder Unterführungen sollten nicht Level 0 haben. Auch bei komplizierten Verzweigungen sollten die Levels den tatsächlichen Zustand widerspiegeln. Trifft man auf Segmente, die bereits im Level verändert wurden, muss man dem Drumherum besondere Aufmerksamkeit schenken, damit nicht fehlerhafte Levels entstehen an Straßen, die bereits korrekt erstellt wurden. In den meisten einfachen Fällen können Probleme beseitigt werden, wenn man den Level eines Segments ändert. Bei komplizierten Kreuzungen kann es hilfreich sein, eine Zeichung zu erstellen oder man schaut sich zuerst die höchst- oder tiefstliegendsten Segmente an, um sich Klarheit zu verschaffen. Gelegentlich kommt man auch an eine Kreuzung, wo die Levels auf den ersten Blick keinen Sinn ergeben. Es kann daher hilfreich sein, ein Segment durch eine Kreuzung zu unterteilen. Es bleibt dann zu hoffen, dass nicht jemand die Kreuzung löscht ohne sich vorher zu vergewissern, wieso die da ist. ==== Ebenen in Straßen ==== Egal welche Ebene eine Straße besitzt, wenn sie durch eine Kreuzung verbunden wird, wird die ganze Verzweigung navigierbar. Wenn man eine Über- oder Unterführung findet, die mit der darüber- oder darunterliegenden Straße durch eine Kreuzung verbunden ist, so ist diese Kreuzung zu löschen. Waze navigiert die Benutzer sonst von einer Brücke auf eine draunterliegende Straße (oder umgekehrt), was nicht sehr sinnvoll ist. Man vergewissert sich dabei zuerst, ob die Ebenen der kreuzenden Straßen und die Benennung der einzelnen Segmente gleich sind. Ansonsten kann die Kreuzung nicht gelöscht werden. Desweiteren kann man dies auch mit der Brücken-Funktion beheben. ==== Brücken-Funktion ==== Zwei Segmente, die über- oder unterführen auswählen und das Brückensymbol anklicken. Die beiden Segmente vereinen sich und der Level erhöht sich automatisch auf Level 1. Falls damit kein Erfolg erzielt wird muss man allf. die Segmente einzeln abtrennen und neu verbinden. Verbindest Du mit der Brücken-Funktion Segmente, die unterschiedliche Levels besitzen, erhöht sich der Level um einen höher, als das Segment mit dem höchsten Level. ==== Für Normalverkehr gesperrt oder zeitlich gebundene Fahrverbote ==== Inzwischen unterstützt Waze auch zeitlich gebundene Fahrverbote, Richtungswechsel zu bestimmten Zeiten oder Straßen, die für bestimmte Fahrzeuge reserviert sind. Diese Straßen haben manchmal eigene Einfahrten und führen parallel entlang normaler Straßen. Das Routing kann dadurch Anweisungen geben, die falsch sind oder gar tödlich enden können! Die einfachste Lösung war bisher, diese Straßen zu löschen, falls sie bereits erstellt wurden. Dies ist jedoch nicht erwünscht. Daher ist es sinnvoll, die erweiterten Eigenschaften möglichst überall hinzuzufügen. ===Wann sind Ramps an Kreuzungen zu verwenden=== Siehe hier [[Abbiegespuren]] ===Wann ein Kreisverkehr erstellt werden soll=== Wenn klar ist, wie man [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehre]] erstellt, ist es die richtige Zeit alle Kreisel, die nur aus einzelnen Straßen Segmenten gezeichnet wurden auszutauschen und durch richtige Kreisverlehre zu ersetzen. Das gleiche gilt für Kreisverkehre der Basis-Karte (Base Map), die ganz leicht an ihrer seltsam eckigen Form erkannt werden können. Spätestens nach dem Korrigieren wird einem klarwerden, wie die [[Erstellen und bearbeiten eines Kreisverkehrs|korrekten Ansagen]] bei der Navigation zustandekommen. ===Richtung und Sperren von Straßen=== '''Wozu sperrt man Segmente?''' Die "Sperren"-Funktion bewirkt gem. [[Häufig gestellte Fragen#Was ist eine gesperrte Straße im Waze Map-Editor.3F|den Häufig gestellten Fragen]] folgendes: * Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]]. * Zwingt das Routing, den verbundenen Segmenten zu folgen und macht es nahezu unmöglich, gegen die definierte Fahrtrichtung zu Routen. '''Wann sperrt man Segmente?''' ''[[Wichtig: Unvollständige Segmente werden nicht gesperrt.]]'' Grundsätzlich bleiben Straßen frei. Waze lebt von den Beiträgen vieler, und jeder soll die Möglichkeit behalten, aktuelle Änderungen an Straßen schnell und einfach einzutragen. Sperren sollten also nur auf wichtigen Straßen vorgenommen werden, wo durch die Bearbeitung durch Einsteiger gravierende Auswirkungen, insbesondere auf den überregionalen Verkehr zu befürchten sind. Folgende Straßen müssen gelockt werden, wenn sie vollständig bearbeitet sind: * Autobahnen samt den zugehörigen Auf- und Abfahrten: Level 4 oder 5 * Bundesstraßen: Level 3 Wenn diese Straßen durch einen Editor niedrigen Ranges erstellt oder bearbeitet wurden, fordert er die Sperrung mit dem richtigen Level im Forum an. '''Informiere Dich in den länderspezifischen Wikis über die Gegebenheiten im betreffenden Land!''' ===Konnektivität=== Nur weil sich zwei Segmente an einer Kreuzung berühren, heißt dies noch nicht, dass sie auch korrekt miteinander verbunden sind. Abbiegeverbote kontrollieren! ===Unnötige Kreuzungen=== Unnötige Kreuzungen sind zu entfernen, da sie oft zu fehlerhaften Verbindungen und falschen Straßennamen führen. Zudem sind sie für das [[Wie Waze Routen kalkuliert|Routing]] nicht von Vorteil, da pro Kreuzung ein Zuschlag von 5 Sekunden zur Fahrzeitberechnung addiert wird. Ausnahmen bilden Orts- oder Landesgrenzen, oder wenn man in Kürze eine Straße mit einer Kreuzung verbindet. Wenn Kreuzungen entfernt werden, muss darauf geachtet werden, dass die Segmente die gleichen Eigenschaften besitzen. Andernfalls kann die Kreuzung nicht entfernt werden. Kreuzungen auf Straßen mit der Eigenschaft "Unbekannt" können aus Sicherheitsgründen nicht gelöscht werden. Straßen in Richtung ändern und nach dem Entfernen der Kreuzung allf. wieder auf "Unbekannt" setzen. ==Neue Straßen== ===Aufzeichnen mit der Waze-App=== Nach dem Aufzeichnen muss die Straße im Editor bearbeitet werden. Aufgezeichnete und unbearbeitete Straßen tauchen zwar in der App auf, sie werden aber nicht für das Routing benutzt. '''Man sollte diesen Anweisungen folgen:''' # Geometrie ausrichten anhand der Luftaufnahme, sofern diese am richtigen Ort ist in der Gegend. Dies sollte mit der Ebene GPS-Punkte geprüft werden. Kanten und Ecken abrunden wo nötig. # Korrekter Straßentyp und Name anhand der Definition des Landes einfügen. # Die korrekte Fahrtrichtung bestimmen. # Kreuzungen hinzufügen und Straßen korrekt verbinden. Wenn mit dem Bearbeiten einer neuen Straße (rot) begonnen wird, wird die Straße ohne Typenänderung weiß erscheinen. Nach dem nächsten Kartenupdate von Waze, wird diese dann auf der Echtzeit-Karte und der Waze-App zu sehen sein. Daher ist es nicht sehr hilfreich, eine unfertige Straße zu hinterlassen. Solange sie rot ist, merkt mann noch, dass die Straße bearbeitet werden muss. Aber sobald sie weiß wird, kann sie im Karteneditor nicht mehr so schnell identifiziert werden. Wenn sie nur weiß ist und auch einen Straßennamen hat, mag dies gut aussehen, aber Waze weiß vielleicht noch nicht, dass die Straße befahren werden kann. ==Parkings und Parkplätze== Das Zuordnen eines Parkplatzes und dessen Straßen dient zwei Zwecken: *es erlaubt Waze eine Tür-zu-Tür-Navigation innerhalb des Parkplatzes *es erlaubt Waze von einer Hauptstraße weg zu navigieren, um fehlerhafte Verkehrsmeldungen zu vermeiden ====Gebrauch des "Parkplatz"-Straßentyps==== "Parkplatz" ermöglicht das Erstellen von Parkplätzen und verhindert gleichzeitig, dass der Routing-Server diese für die Navigation miteinbezieht. Damit nicht durch Parkplätze geroutet wird, hat Waze den Routing-Algorithmus im Juni 2012 geändert. Jedes Segment, das sich innerhalb eines Parkplatzes befindet ist daher als "Parkplatz" zu definieren. ====Einkaufszentren==== Wenn ein Parkplatz eines Einkaufszentrums erstellt wird, sollten Haupteinfahrten und die wichtigsten Verbindungen erstellt werden, Verbindungen zwischen verschiedenen Parzellen eines Parkplatzes und entlang der Geschäfte. Die meistgebrauchten Spuren sollten dabei miteinbezogen werden. Am wichtigsten sind hier Benutzerfreundlichkeit und Einfachheit. Es macht keinen Sinn, jedes einzelne Parkfeld mit einem Segment zu bestücken, dies lässt die Karte auf der App nur unübersichtlich aussehen. ====Kleinere Parkplätze==== Parkplätze, die einer kleinen Anzahl von Unternehmen dienen, sollten minimal sein. Genug, um dem Fahrer richtige Richtungen, Ein- und Ausfahrten zu zeigen und den Weg zu einem Geschäft. Manchmal reicht ein einziges paralleles Segment. ====Durchfahrts-Parkplätze==== Diese sollten nicht zu viele Einbahnen enthalten und am besten mit einer Einbahn als Schlaufe durch den Parkplatz führen. Man bedenke dabei, dass sich eine [[WME Schnellstart-Anleitung#Straßen-Schlaufen|Straße]] nicht mit sich selbst verbindet. ====Parkhäuser==== Wenn ein Parkhaus nur eine Ein- und Ausfahrt besitzt, sollte diese mindestens auf der Karte erscheinen. Ein einzelnes zweispuriges Segment reicht aus, da im Parkhaus meistens kein GPS-Signal vorhanden ist. Der Straßentyp ist "Parkplatz" und das Parkhaus kann mit einem Orientierungspunkt versehen werden. Besitzt das Parkhaus separate Ein- und Ausfahrten, so sollte eine Durchfahrt ermöglicht werden. Dazu reicht in den meisten Fällen ein einziges Segment. Es ist nicht nötig, jedes Stockwerk des Parkhauses darzustellen, dies macht die Karte nur unnötig unübersichtlich. =Unterdrücken von Verkehrsmeldungen und Kartenfehlern= Straßentyp "Parkplatz", Orientierungspunkte "Parkplatz" und "Tankstelle" verhindern serverseitig die Entstehung von Kartenfehlern.<br> Orientierungspunkte "Parkplatz" und "Tankstelle" verhindern eine Staumeldung, daher dürfen sie nicht an angrenzende Haupt- oder Straßen herangezeichnet werden, sondern dürfen nur den Parkplatz oder die Tankstelle selbst einschließen. =Klassifizierung von Kreuzungen= Verschiedene Arten von Kreuzungen haben [[Classification of crossings|Standard-Möglichkeiten]], um diese zu bearbeiten. Interessant sind auch diese Seiten:<br> [[Kreuzungen]]<br> [[Abbiegespuren]]<br> [[Limited Access Interchange Style Guide]] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] b8d0c3c9720028b2d5abffc1836146d28a6b7859 10 46 150 2014-01-29T01:59:30Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Stop point''' may refer to: * Stop point, used with [[House_Numbers_in_WME#Setting_the_Stop_Point|house numbers]] for navigation * Stop point, used in [[How_to_Navigate#Add_a_stop_point|navigation]] to go to multiple destinations in order {{Disambig}} 139c49d806a01e9ebd92a321152d05a04b7978a6 10 48 156 2014-01-29T02:00:16Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[Stop point]] 69ecf03a450d8b37061308298a5bca1254900685 10 47 154 2014-01-29T02:00:51Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[Stop point]] 69ecf03a450d8b37061308298a5bca1254900685 10 49 158 2014-01-29T02:01:14Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[Stop point]] 69ecf03a450d8b37061308298a5bca1254900685 10 38 116 2014-01-29T02:14:26Z Kentsmith9 25 Created redirect wikitext text/x-wiki '''Points''' typically refer to: * [[Your_Rank_and_Points|Points]], the collection and counting of credits related to Waze usage and editing See also: * [[Nodes]] * [[Stop point]] {{Disambig}} 5104c244b5f098870a14984543597ee7aaa70370 117 116 2014-01-29T02:15:10Z Kentsmith9 25 fixed link wikitext text/x-wiki '''Points''' typically refer to: * [[Your_Rank_and_Points|Points]], the collection and counting of credits related to Waze usage and editing See also: * [[Node]] * [[Stop point]] {{Disambig}} 9aa646d1c35c6cb9ce8917f81c112b8ff4474a5a 118 117 2014-01-29T02:23:34Z Kentsmith9 25 added link wikitext text/x-wiki '''Points''' typically refer to: * [[Your_Rank_and_Points|Points]], the collection and counting of credits related to Waze usage and editing See also: * [[Junction point]] * [[Node]] * [[Stop point]] {{Disambig}} 685cc240ba97b4e61b5ea0d328f3758ddd2e72c1 119 118 2014-02-01T03:57:33Z Kentsmith9 25 Merged with Points wikitext text/x-wiki '''Points''' typically refer to: * [[Your_Rank_and_Points|Points]], the collection and counting of credits related to Waze usage and editing * Points, the elements often confused with [[nodes]] See also: * [[Junction point]] * [[Stop point]] {{Disambig}} f03712bc3aab5e3f4df209b01295d11b22d87710 10 39 127 126 2014-02-01T03:53:37Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Points''' may refer to: * [[Your_Rank_and_Points|Points]], the collection and counting of credits related to Waze usage and editing * Points, the elements often confused with [[nodes]] See also [[Stop point]] {{Disambig}} 2e9b93e8e021f3e6c451c94a00a253d41e024da3 128 127 2014-02-01T03:58:06Z Kentsmith9 25 Changed to redirect wikitext text/x-wiki #REDIRECT [[Points (disambiguation)]] a7dc21c9befee8c7d1eaf6291a44952ff7aefe24 11475 11474 2014-02-03T02:29:20Z Kentsmith9 25 Moved doc to separate page wikitext text/x-wiki <div style="clear:{{{1|both}}};"></div><noinclude>{{doc}}</noinclude> 15e943687be5d8f8e27fa6cc7813bbfa85df72a9 10 40 129 2014-02-03T05:27:52Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Rank''' may refer to: * Lock rank, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's rank * [[Your_Rank_and_Points#Map_editing_rank|Map Editing Rank]] relative to other editors See also: [[Level]] {{Disambig}} 63289430b344dbdb04f74c406ea8fc6161fc985b 0 12 27 2014-02-03T18:08:22Z Kentsmith9 25 Created redirect wikitext text/x-wiki {{NeedPage}} {{red|Just need a redirect to correct page}} 4892895b92a079b9edb513e130bf2d01f84ea09f 10 68 251 250 2014-02-04T16:37:55Z Kentsmith9 25 Kentsmith9 moved page [[Abbreviations & Acronyms]] to [[Abbreviations and acronyms]]: Removing ampersand wikitext text/x-wiki ==Other Abbreviations== ''' ''Prefixes, directional abbreviations and other (non-suffix) abbreviations should not be used, except for state/ territory abbreviations & country abbreviations; under ISO 3166-1 alpha-3.'' ''' 1. Prefix abbreviations include: Mount (Mt.), and Saint (St.) Note: Mount (Mt.) is not the same as Mountain (Mtn.). :*Although they are common, can cause issues as variation and overlap exists between naming, usage, and prefix standards (I.e. What words to, and how to, abbreviate). :*Therefore a lake named "Lake Clair" would not be abbreviated, while if its documented name was "Clair Lake" it would be. 2. Directional abbreviations include: East (E), South West (SW), Central (CN), Upper (UP), and Lower (LR). :*In addition to not being abbreviated, directions should only be included when they are a part of the documented name, and not a suffix or prefix added at a later stage to describe location or orientation/ direction. 3. Other abbreviations include: Island (Is.), Quay (Qy), Reserve (Res) and Tunnel (Tunl). :*These are acceptable to be used when they are a suffix, but not acceptable when they are place names. :*Therefore "King-Tunnel Road" should have tunnel spelt in full, as it refers to a tunnel. While "Queen Tunnel-Road" could have tunnel abbreviated, as tunnel refers to the type of roadway, and is a part of the suffix. :*Likewise an Island named "Island Island" would be abbreviated to Island Is. 4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category. :*For example: California would be abbreviated to C.A. not CA and Victoria to VIC. :*Country abbreviations are done under "ISO 3166-1 alpha-3". Further information can be found on Wikipedia. ([http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 ISO 3166:]) :*Other regions include that of Suburbs, Districts, Localities, Shires and special purpose areas. (I.e. Indigenous, Military and Airport areas.) ==Standard Suffix Abbreviations== Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road"). '''Notes:''' 1. Only abbreviate suffixes. :*"The Avenue", "The Green ", and etc. should not be abbreviated. :*"Circuit Avenue Road" would be abbreviated to Circuit Avenue Rd and not "Cct Ave Rd" :*A road named "Service way" should not be abbreviated, while "Pipeline Service way" should be. 2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens). 3. In the event that the original suffix is a plural (I.e contains a "s" at the end) and only its singular form is present as an abbreviation, simply add an "s" to the end of the abbreviation. Legend: # TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Untested |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mount|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pky|| Yes |- | Parkways||Pkys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Untested |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further Reading== === Forums === Please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: http://www.waze.com/forum/viewtopic.php?f=10&t=15178 === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. 7647171cc38f1275ccc2fc872429b7d3dc22b77c 252 251 2014-02-04T16:39:05Z Kentsmith9 25 /* Forums */ named hyperlink wikitext text/x-wiki ==Other Abbreviations== ''' ''Prefixes, directional abbreviations and other (non-suffix) abbreviations should not be used, except for state/ territory abbreviations & country abbreviations; under ISO 3166-1 alpha-3.'' ''' 1. Prefix abbreviations include: Mount (Mt.), and Saint (St.) Note: Mount (Mt.) is not the same as Mountain (Mtn.). :*Although they are common, can cause issues as variation and overlap exists between naming, usage, and prefix standards (I.e. What words to, and how to, abbreviate). :*Therefore a lake named "Lake Clair" would not be abbreviated, while if its documented name was "Clair Lake" it would be. 2. Directional abbreviations include: East (E), South West (SW), Central (CN), Upper (UP), and Lower (LR). :*In addition to not being abbreviated, directions should only be included when they are a part of the documented name, and not a suffix or prefix added at a later stage to describe location or orientation/ direction. 3. Other abbreviations include: Island (Is.), Quay (Qy), Reserve (Res) and Tunnel (Tunl). :*These are acceptable to be used when they are a suffix, but not acceptable when they are place names. :*Therefore "King-Tunnel Road" should have tunnel spelt in full, as it refers to a tunnel. While "Queen Tunnel-Road" could have tunnel abbreviated, as tunnel refers to the type of roadway, and is a part of the suffix. :*Likewise an Island named "Island Island" would be abbreviated to Island Is. 4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category. :*For example: California would be abbreviated to C.A. not CA and Victoria to VIC. :*Country abbreviations are done under "ISO 3166-1 alpha-3". Further information can be found on Wikipedia. ([http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 ISO 3166:]) :*Other regions include that of Suburbs, Districts, Localities, Shires and special purpose areas. (I.e. Indigenous, Military and Airport areas.) ==Standard Suffix Abbreviations== Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road"). '''Notes:''' 1. Only abbreviate suffixes. :*"The Avenue", "The Green ", and etc. should not be abbreviated. :*"Circuit Avenue Road" would be abbreviated to Circuit Avenue Rd and not "Cct Ave Rd" :*A road named "Service way" should not be abbreviated, while "Pipeline Service way" should be. 2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens). 3. In the event that the original suffix is a plural (I.e contains a "s" at the end) and only its singular form is present as an abbreviation, simply add an "s" to the end of the abbreviation. Legend: # TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Untested |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mount|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pky|| Yes |- | Parkways||Pkys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Untested |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further Reading== === Forums === Please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: [http://www.waze.com/forum/viewtopic.php?f=10&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. d20e80b199b0fee09258150eef58586ccac9fc03 253 252 2014-02-04T16:40:02Z Kentsmith9 25 /* Forums */ clarified wikitext text/x-wiki ==Other Abbreviations== ''' ''Prefixes, directional abbreviations and other (non-suffix) abbreviations should not be used, except for state/ territory abbreviations & country abbreviations; under ISO 3166-1 alpha-3.'' ''' 1. Prefix abbreviations include: Mount (Mt.), and Saint (St.) Note: Mount (Mt.) is not the same as Mountain (Mtn.). :*Although they are common, can cause issues as variation and overlap exists between naming, usage, and prefix standards (I.e. What words to, and how to, abbreviate). :*Therefore a lake named "Lake Clair" would not be abbreviated, while if its documented name was "Clair Lake" it would be. 2. Directional abbreviations include: East (E), South West (SW), Central (CN), Upper (UP), and Lower (LR). :*In addition to not being abbreviated, directions should only be included when they are a part of the documented name, and not a suffix or prefix added at a later stage to describe location or orientation/ direction. 3. Other abbreviations include: Island (Is.), Quay (Qy), Reserve (Res) and Tunnel (Tunl). :*These are acceptable to be used when they are a suffix, but not acceptable when they are place names. :*Therefore "King-Tunnel Road" should have tunnel spelt in full, as it refers to a tunnel. While "Queen Tunnel-Road" could have tunnel abbreviated, as tunnel refers to the type of roadway, and is a part of the suffix. :*Likewise an Island named "Island Island" would be abbreviated to Island Is. 4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category. :*For example: California would be abbreviated to C.A. not CA and Victoria to VIC. :*Country abbreviations are done under "ISO 3166-1 alpha-3". Further information can be found on Wikipedia. ([http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 ISO 3166:]) :*Other regions include that of Suburbs, Districts, Localities, Shires and special purpose areas. (I.e. Indigenous, Military and Airport areas.) ==Standard Suffix Abbreviations== Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road"). '''Notes:''' 1. Only abbreviate suffixes. :*"The Avenue", "The Green ", and etc. should not be abbreviated. :*"Circuit Avenue Road" would be abbreviated to Circuit Avenue Rd and not "Cct Ave Rd" :*A road named "Service way" should not be abbreviated, while "Pipeline Service way" should be. 2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens). 3. In the event that the original suffix is a plural (I.e contains a "s" at the end) and only its singular form is present as an abbreviation, simply add an "s" to the end of the abbreviation. Legend: # TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Untested |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mount|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pky|| Yes |- | Parkways||Pkys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Untested |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further Reading== === Forums === If you have further questions on this topic, please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: [http://www.waze.com/forum/viewtopic.php?f=10&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. 317846ed5146d62bb61618b416f1402c8d22e7cd 254 253 2014-02-04T16:44:44Z Kentsmith9 25 Created intro section wikitext text/x-wiki This page covers the abbreviations and acronyms used in naming roads in Waze. By following these guidelines the Text-to-speech (TTS) feature will work at its optimum level. If you have questions about these instructions, see the [[Abbreviations_and_acronyms#Further reading|further reading]] at the bottom of this page. ==Other Abbreviations== ''' ''Prefixes, directional abbreviations and other (non-suffix) abbreviations should not be used, except for state/ territory abbreviations & country abbreviations; under ISO 3166-1 alpha-3.'' ''' 1. Prefix abbreviations include: Mount (Mt.), and Saint (St.) Note: Mount (Mt.) is not the same as Mountain (Mtn.). :*Although they are common, can cause issues as variation and overlap exists between naming, usage, and prefix standards (I.e. What words to, and how to, abbreviate). :*Therefore a lake named "Lake Clair" would not be abbreviated, while if its documented name was "Clair Lake" it would be. 2. Directional abbreviations include: East (E), South West (SW), Central (CN), Upper (UP), and Lower (LR). :*In addition to not being abbreviated, directions should only be included when they are a part of the documented name, and not a suffix or prefix added at a later stage to describe location or orientation/ direction. 3. Other abbreviations include: Island (Is.), Quay (Qy), Reserve (Res) and Tunnel (Tunl). :*These are acceptable to be used when they are a suffix, but not acceptable when they are place names. :*Therefore "King-Tunnel Road" should have tunnel spelt in full, as it refers to a tunnel. While "Queen Tunnel-Road" could have tunnel abbreviated, as tunnel refers to the type of roadway, and is a part of the suffix. :*Likewise an Island named "Island Island" would be abbreviated to Island Is. 4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category. :*For example: California would be abbreviated to C.A. not CA and Victoria to VIC. :*Country abbreviations are done under "ISO 3166-1 alpha-3". Further information can be found on Wikipedia. ([http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 ISO 3166:]) :*Other regions include that of Suburbs, Districts, Localities, Shires and special purpose areas. (I.e. Indigenous, Military and Airport areas.) ==Standard Suffix Abbreviations== Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road"). '''Notes:''' 1. Only abbreviate suffixes. :*"The Avenue", "The Green ", and etc. should not be abbreviated. :*"Circuit Avenue Road" would be abbreviated to Circuit Avenue Rd and not "Cct Ave Rd" :*A road named "Service way" should not be abbreviated, while "Pipeline Service way" should be. 2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens). 3. In the event that the original suffix is a plural (I.e contains a "s" at the end) and only its singular form is present as an abbreviation, simply add an "s" to the end of the abbreviation. Legend: # TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Untested |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mount|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pky|| Yes |- | Parkways||Pkys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Untested |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further reading== === Forums === If you have further questions on this topic, please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: [http://www.waze.com/forum/viewtopic.php?f=10&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. e30287d6a97debb1f386b2edffc6b234a1be7f7d 255 254 2014-02-04T17:15:02Z Kentsmith9 25 Convert section names to lowercase per Wiki guidelines wikitext text/x-wiki This page covers the abbreviations and acronyms used in naming roads in Waze. By following these guidelines the Text-to-speech (TTS) feature will work at its optimum level. If you have questions about these instructions, see the [[Abbreviations_and_acronyms#Further reading|further reading]] at the bottom of this page. ==Other abbreviations== ''' ''Prefixes, directional abbreviations and other (non-suffix) abbreviations should not be used, except for state/ territory abbreviations & country abbreviations; under ISO 3166-1 alpha-3.'' ''' 1. Prefix abbreviations include: Mount (Mt.), and Saint (St.) Note: Mount (Mt.) is not the same as Mountain (Mtn.). :*Although they are common, can cause issues as variation and overlap exists between naming, usage, and prefix standards (I.e. What words to, and how to, abbreviate). :*Therefore a lake named "Lake Clair" would not be abbreviated, while if its documented name was "Clair Lake" it would be. 2. Directional abbreviations include: East (E), South West (SW), Central (CN), Upper (UP), and Lower (LR). :*In addition to not being abbreviated, directions should only be included when they are a part of the documented name, and not a suffix or prefix added at a later stage to describe location or orientation/ direction. 3. Other abbreviations include: Island (Is.), Quay (Qy), Reserve (Res) and Tunnel (Tunl). :*These are acceptable to be used when they are a suffix, but not acceptable when they are place names. :*Therefore "King-Tunnel Road" should have tunnel spelt in full, as it refers to a tunnel. While "Queen Tunnel-Road" could have tunnel abbreviated, as tunnel refers to the type of roadway, and is a part of the suffix. :*Likewise an Island named "Island Island" would be abbreviated to Island Is. 4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category. :*For example: California would be abbreviated to C.A. not CA and Victoria to VIC. :*Country abbreviations are done under "ISO 3166-1 alpha-3". Further information can be found on Wikipedia. ([http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 ISO 3166:]) :*Other regions include that of Suburbs, Districts, Localities, Shires and special purpose areas. (I.e. Indigenous, Military and Airport areas.) ==Standard suffix abbreviations== Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road"). '''Notes:''' 1. Only abbreviate suffixes. :*"The Avenue", "The Green ", and etc. should not be abbreviated. :*"Circuit Avenue Road" would be abbreviated to Circuit Avenue Rd and not "Cct Ave Rd" :*A road named "Service way" should not be abbreviated, while "Pipeline Service way" should be. 2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens). 3. In the event that the original suffix is a plural (I.e contains a "s" at the end) and only its singular form is present as an abbreviation, simply add an "s" to the end of the abbreviation. Legend: # TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Untested |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mount|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pky|| Yes |- | Parkways||Pkys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Untested |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further reading== === Forums === If you have further questions on this topic, please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: [http://www.waze.com/forum/viewtopic.php?f=10&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. c10b7beb9c628a81f4afe2adb21f0e393dbda76b 0 69 277 2014-02-04T16:37:56Z Kentsmith9 25 Kentsmith9 moved page [[Abbreviations & Acronyms]] to [[Abbreviations and acronyms]]: Removing ampersand wikitext text/x-wiki #REDIRECT [[Abbreviations and acronyms]] 474590d763e7e7bda332a8deb4d6c7a2b9529e13 0 71 281 280 2014-02-04T16:50:08Z Kentsmith9 25 Replaced ampersand wikitext text/x-wiki #REDIRECT [[Abbreviations and acronyms]] 474590d763e7e7bda332a8deb4d6c7a2b9529e13 0 70 278 2014-02-04T16:51:00Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Abbreviations and acronyms]] 474590d763e7e7bda332a8deb4d6c7a2b9529e13 0 72 282 2014-02-04T16:51:27Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Abbreviations and acronyms]] 474590d763e7e7bda332a8deb4d6c7a2b9529e13 10 58 11736 11735 2014-02-11T09:24:52Z Kentsmith9 25 Added blue construction type wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | important = Mbox important.png | warning = mbox_warning_yellow.png | caution = Edit-clear.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | notice <!-- notice = default --> | construction = Warning blue construction.png | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table> 49649c30947041280de955ed2e91da9476748453 187 186 2014-02-19T06:45:11Z Kentsmith9 25 Kentsmith9 moved page [[Zoom]] to [[Zoom (disambiguation)]] wikitext text/x-wiki '''Zoom''' may refer to: * [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom control]], the interface in the WME to set the visual zoom of the map * [[Map_Editor_Interface_and_Controls#Scale|Zoom scale]] or zoom level, the meter or feet measurement associated in WME * [[Auto zoom|Auto zoom]], automatically controls the map resolution in the Waze application * [[Zoom control (app)|Zoom control (app)]], manually sets the map resolution in the Waze application {{Disambig}} 2f2bcb05deca08261a4358c3790d5cb069c7b7e6 10 43 139 2014-02-15T08:44:01Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Search''' may refer to: * [[How_to_Navigate|Search]], in the client app * [[Map_Editor_Interface_and_Controls#Search_box|Search]], in the Waze Map Editor * Search, in the [http://www.waze.com/livemap/ Live Map] * [[Search_forum_for_common_words|Search]], in the Forums using Google * [[Bugzilla_how_to_guide#Searching|Search]], in Waze Bugzilla * [[Search codes]], used to change functions in the client app {{Disambig}} 150af8f6047acb342dbc280e636fa29e888f61fa 140 139 2014-02-19T06:41:42Z Kentsmith9 25 Kentsmith9 moved page [[Search]] to [[Search (disambiguation)]] wikitext text/x-wiki '''Search''' may refer to: * [[How_to_Navigate|Search]], in the client app * [[Map_Editor_Interface_and_Controls#Search_box|Search]], in the Waze Map Editor * Search, in the [http://www.waze.com/livemap/ Live Map] * [[Search_forum_for_common_words|Search]], in the Forums using Google * [[Bugzilla_how_to_guide#Searching|Search]], in Waze Bugzilla * [[Search codes]], used to change functions in the client app {{Disambig}} 150af8f6047acb342dbc280e636fa29e888f61fa 10 68 257 256 2014-02-16T08:32:34Z Kentsmith9 25 Moved section 'Other abbreviations' to talk page until it is discussed in the forums. wikitext text/x-wiki This page covers the abbreviations and acronyms used in naming roads in Waze. By following these guidelines the Text-to-speech (TTS) feature will work at its optimum level. If you have questions about these instructions, see the [[Abbreviations_and_acronyms#Further reading|further reading]] at the bottom of this page. ==Standard suffix abbreviations== Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road"). '''Notes:''' 1. Only abbreviate suffixes. :*"The Avenue", "The Green ", and etc. should not be abbreviated. :*"Circuit Avenue Road" would be abbreviated to Circuit Avenue Rd and not "Cct Ave Rd" :*A road named "Service way" should not be abbreviated, while "Pipeline Service way" should be. 2. Suffix abbreviations do not contain any punctuation, such as "." (Full-stops) or "-" (Hyphens). 3. In the event that the original suffix is a plural (I.e contains a "s" at the end) and only its singular form is present as an abbreviation, simply add an "s" to the end of the abbreviation. Legend: # TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Untested |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mount|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pky|| Yes |- | Parkways||Pkys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Untested |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further reading== UK editors should see [[How to classify and name roads (United_Kingdom)#Abbreviations|How to classify and name roads (United_Kingdom)]] for UK specific abbreviations, some of which differ. === Forums === If you have further questions on this topic, please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: [http://www.waze.com/forum/viewtopic.php?f=10&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. dd2de237cdd25dd628b5ac15e2f2bb59df557f03 10 75 370 369 2014-02-17T03:29:13Z Kentsmith9 25 /* Required Reading */ Fixed links wikitext text/x-wiki <span style="color: red;">''The specific details of the Area Manager role are currently under review within the Waze community. Some of the information below is currently out of date. Please review the [http://www.waze.com/forum forums] for more information. Once the role changes are finalized, this section will be updated as required.''</span><br> An Area Manager, AM for short, is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: * Respond to and correct user update requests on the [[Update Requests in Waze Map Editor| Update Requests]] layer. * Process and resolve map errors/problems as shown on the [[Map Problems in Waze Map Editor| Map Problems]] layer. * Make changes to the map when road construction projects start and finish by maintaining new geometry, adding or deleting roads and disconnecting and re-connecting ramps. * Maintain speed and red-light cameras, processing reports of devices from Waze drivers. * Act as a mentor to other editors, offering advice in both the forums and when you see improper edits on the map. ==How to Become an Area Manager== The position of Area Manager is by appointment. To become an area manager, you must meet the prerequisites and then submit your application. Prospective Area Managers should already... * have at least a few months of experience editing the Waze maps regularly. * have read and followed the guidelines for mapping found in the wiki, starting at the Waze Map Editing page. * have completed at least 5000 quality edits. * have a real Waze username which does not start with usa_ or world_. * have their state and/or country in their forum profile. * have forum PMs enabled and associated with a valid and verifiable email address. * be active in the Waze forums, asking questions, and even providing guidance for newer editors, if possible. * know who their regional coordinator is. (Knowing the correct answer to this is a strong indicator as to how much reading an applicant has done of the forums and Wiki). ===Required Reading=== Before applying to become an AM, you will be expected to have read the following wiki pages and forums. '''Wiki''' * [[Map Editing Quick-start Guide]] * [[Best map editing practice]] * [[Map Editing Tips and Hints]] * [[Waze_Map_Editor| Waze Map Editor]] and all the [[Waze_Map_Editor#Editing_Manual| Editing Manual]] links therein ''Be sure to also find and read the editing guidelines specific to your country.'' '''Forum''' You should also read these two forums and know where the Unlock Request is located * [http://www.waze.com/forum/viewtopic.php?f=636&t=45237| READ ME FIRST! General forum guidelines] * [http://www.waze.com/forum/viewtopic.php?t=32072| Unlock Request Instructions] * [http://www.waze.com/forum/viewforum.php?f=265| Unlock Request] ==Area Manager application process== ====Identifying your area==== Before you head off to submit your application for AM, use the [[Map_Editing_(new_Editor)|Waze Map Editor]], position the map and set the zoom level to show the area you want to manage. Make a [[Map_Editing_(new_Editor)#Permalink|Permalink]] of the area and copy the address from the address bar in your browser. ===Area Manager territory=== * More than one Area Manager can manage the same area. * Areas can overlap, be smaller or larger. * You can also be the AM for more than one area. Notice the green area of the map has four managers. [[Image:AreaManagerLayer.png]] ===The application=== If you would like to become an Area Manager, or expand your existing area, you will need to '''complete the appropriate application form for your country'''. The following countries have a self management system and requests will be approved by country managers or coordinators. ''Please go to the relevant [http://www.waze.com/forum/viewforum.php?f=19 country forum] to find the appropriate application form:'' * [http://www.waze.com/forum/viewforum.php?f=645 USA] * [http://www.waze.co.il/forum/viewforum.php?f=38 Israel] * [http://www.waze.com/forum/viewforum.php?f=55 United Kingdom] * [http://www.waze.com/forum/viewforum.php?f=25 Hungary] * [http://world.waze.com/forum/viewforum.php?f=26 Spain] * [http://www.waze.com/forum/viewforum.php?f=279 Malaysia] / [http://www.waze.com/forum/viewforum.php?f=191 Singapore] / Brunei * [http://www.waze.com/forum/viewforum.php?f=331 Brazil] * [http://www.waze.com/forum/viewforum.php?f=20 Italy] * [http://www.waze.com/forum/viewforum.php?f=700 Belgium] / [http://www.waze.com/forum/viewforum.php?f=21 The Netherlands] / [http://www.waze.com/forum/viewforum.php?f=381 Luxembourg] * [http://www.waze.com/forum/viewforum.php?f=24 Germany / Austria / Switzerland] * [http://www.waze.com/forum/viewforum.php?f=34 France] * [http://www.waze.com/forum/viewforum.php?f=440 Chile] * [http://www.waze.com/forum/viewforum.php?f=611 Portugal] * [http://www.waze.com/forum/viewforum.php?f=22 Czech republic & Slovakia] * [http://www.waze.com/forum/viewforum.php?f=465 Mexico] * [http://www.waze.com/forum/viewforum.php?f=33 Sweden] * [http://www.waze.com/forum/viewforum.php?f=309 Philippines] * [http://www.waze.com/forum/viewforum.php?f=171 India] * [http://www.waze.com/forum/viewforum.php?f=120 Romania] * [http://world.waze.com/forum/viewtopic.php?f=56&t=59583 Australia] '''For all other countries''', AM requests should be [https://docs.google.com/a/waze.com/spreadsheet/viewform?formkey=dGl6TVF2bzFtdHRWUDVzR3N5TllZanc6MA#gid=0 submitted via this form] and will be handled directly by Waze support. ==Area Manager Links== * [[Waze Map Editor|Map Editing]] * [[Best map editing practice]] * [[Area Manager: Diagnosis]] * [[Area Manager: Tips and Tricks]] <!-- * [[Area Manager: YouTube Training Videos]]--> * [[Area Manager: How to edit wiki pages]] * [[Known issues]] * Road Types: [[Road_Types_(USA)|(USA)]], [[Road_Types_India| India]] * [[Junction Style Guide| Junction Style Guide]] * [[Area Manager: 101]] ==List of Area Managers== See [http://bit.ly/WazeAMs List of Area Managers and their preferred contact details]. 32eff5ec2d4a450c81176c39d9b46d764975e006 0 21 48 2014-02-17T04:16:57Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Icon''' may refer to: * Wazer icon, as shown in the [[Your_Rank_and_Points#Client_application_rank|client application]] * Forum icon, (or [[Your_Rank_and_Points#Forum_badges|Forum badge]]) appears in right pane of an editor's forum post * Park icon, (or [[Nearing_destination|parking pin]] to mark the location of your vehicle {{Disambig}} 37e6f73ff6bf7af2b719343f8a9d19e95490c8ef 49 48 2014-02-19T06:47:12Z Kentsmith9 25 Kentsmith9 moved page [[Icon]] to [[Icon (disambiguation)]] wikitext text/x-wiki '''Icon''' may refer to: * Wazer icon, as shown in the [[Your_Rank_and_Points#Client_application_rank|client application]] * Forum icon, (or [[Your_Rank_and_Points#Forum_badges|Forum badge]]) appears in right pane of an editor's forum post * Park icon, (or [[Nearing_destination|parking pin]] to mark the location of your vehicle {{Disambig}} 37e6f73ff6bf7af2b719343f8a9d19e95490c8ef 52 51 2014-02-21T20:15:20Z Kentsmith9 25 Changed to reflect redirect change for main article wikitext text/x-wiki '''Icon''' links directly to: * [[Waze symbols]], client app icons for alert, moods (other drivers), ranks, and candy '''Icon''' may also refer to: * Forum icon, (or [[Your_Rank_and_Points#Forum_badges|Forum badge]]) appears in right pane of an editor's forum post * Park icon, (or [[Nearing_destination|parking pin]] to mark the location of your vehicle {{Disambig}} e03f09b4396ebe2373a9622a6d3617c268b2f037 0 23 63 2014-02-17T04:17:27Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Icon]] c5214a83ec0edc7c3072de4bb876a87fd0085d91 64 63 2014-02-21T20:17:22Z Kentsmith9 25 Improved target page wikitext text/x-wiki #REDIRECT [[Waze Symbols]] 72e857ce1d00b04394a52353e44165df1f9875a9 0 19 42 2014-02-17T05:23:06Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''GPS''' may refer to: * [[Entering_GPS_coordinates|GPS]] coordinates, entered in the client app. * [[Map_Editor_Interface_and_Controls#GPS_points|GPS points layer]], in the Waze Map Editor {{Disambig}} 919be0069f1b9ac4b0099fce843ffbca110badf1 43 42 2014-02-17T05:23:39Z Kentsmith9 25 Fixed internal Wikilinks wikitext text/x-wiki '''GPS''' may refer to: * [[Entering_GPS_coordinates|GPS coordinates]], entered in the client app. * [[Map_Editor_Interface_and_Controls#GPS_points|GPS points layer]], in the Waze Map Editor {{Disambig}} 6b736cf69a97234eed359f8f8c11bb658f4774c8 44 43 2014-02-19T06:43:54Z Kentsmith9 25 Kentsmith9 moved page [[GPS]] to [[GPS (disambiguation)]] wikitext text/x-wiki '''GPS''' may refer to: * [[Entering_GPS_coordinates|GPS coordinates]], entered in the client app. * [[Map_Editor_Interface_and_Controls#GPS_points|GPS points layer]], in the Waze Map Editor {{Disambig}} 6b736cf69a97234eed359f8f8c11bb658f4774c8 10 51 166 165 2014-02-19T06:01:51Z Kentsmith9 25 Kentsmith9 moved page [[Toll]] to [[Toll (disambiguation)]]: Disambiguation page clarification wikitext text/x-wiki '''Toll''' may refer to: * [[Best_map_editing_practice#Toll roads|Toll roads]], the best map editing practice for when to create them * [[Creating_and_Editing_street_segments#Toll road|Toll road]], the check box in the Waze Map Editor * [[Avoid toll roads]], the setting in the Waze client app to route without using toll roads {{Disambig}} 00c7ead9cbf5aa54681221b2a0a2b1ca27066617 10 52 172 2014-02-19T06:01:51Z Kentsmith9 25 Kentsmith9 moved page [[Toll]] to [[Toll (disambiguation)]]: Disambiguation page clarification wikitext text/x-wiki #REDIRECT [[Toll (disambiguation)]] 733ad3b390866385a67b3c3e627daead9238408c 0 96 643 642 2014-02-19T06:07:08Z Kentsmith9 25 /* Toll roads */ Added DaB link wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. It would have to be manually looked up and added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and relalign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_ranks#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a transition penalty when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] ed9cff90115490044da3e143c258caa9876c5104 644 643 2014-02-21T17:06:03Z Kentsmith9 25 Double redirect fix wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-turns are required to properly make turns that are blocked by a median. * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * (Just because) Google Maps or other mapping source show it as a split road. Remember that splitting and unsplitting each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. It would have to be manually looked up and added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and relalign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' if you decide to be clever and edit the road properties of multiple segments at a time, familiarize yourself with the [[Best_map_editing_practice#Editing_Multiple_Segments|known problems with mass-editing]] first. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_rank#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a transition penalty when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] 5f1540a9a310240f58463526470fb78a5bd80e85 0 2 3 2 2014-02-19T06:08:15Z Kentsmith9 25 Kentsmith9 moved page [[Address]] to [[Address (disambiguation)]] wikitext text/x-wiki '''Address''' may refer to: * Address, used to look up and edit [[House_Numbers_in_WME|house numbers]] * [[Creating_and_Editing_street_segments#Address_Properties|Address properties]], identifying the country, state, city, and road name of a segment {{Disambig}} ec10ef9a621de370008af0dd316107fc1ab38657 0 3 7 2014-02-19T06:08:15Z Kentsmith9 25 Kentsmith9 moved page [[Address]] to [[Address (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Address (disambiguation)]] 97e6673b8cb0d91c82107d06c6de0af1204ef874 0 12 28 27 2014-02-19T06:14:09Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Editing points''' typically refer to: * [[Your_Rank_and_Points|Editing points]], the collection and counting of credits related to Waze usage and editing * Editing points, making changes to the elements often confused with [[nodes]] See also: * [[Junction point]] * [[Stop point]] {{Disambig}} 1a6d68ed45023efae30c8cdc6b64a021c2fddce7 29 28 2014-02-19T06:14:36Z Kentsmith9 25 Kentsmith9 moved page [[Editing points]] to [[Editing points (disambiguation)]] wikitext text/x-wiki '''Editing points''' typically refer to: * [[Your_Rank_and_Points|Editing points]], the collection and counting of credits related to Waze usage and editing * Editing points, making changes to the elements often confused with [[nodes]] See also: * [[Junction point]] * [[Stop point]] {{Disambig}} 1a6d68ed45023efae30c8cdc6b64a021c2fddce7 0 13 32 2014-02-19T06:14:36Z Kentsmith9 25 Kentsmith9 moved page [[Editing points]] to [[Editing points (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Editing points (disambiguation)]] 9ee5c39e030f9f9827db1301dcea93a190e2059b 0 16 37 36 2014-02-19T06:15:27Z Kentsmith9 25 Kentsmith9 moved page [[Errors]] to [[Errors (disambiguation)]] wikitext text/x-wiki '''Errors''' may refer to: * [[WME errors]], those seen in the Waze Map Editor application * Errors automatically reported by Waze servers and displayed as [[Map_Problems_in_Waze_Map_Editor|map problems in WME]] * Errors reported by Waze application users and displayed as [[Update_Requests_in_Waze_Map_Editor|update requests in WME]] {{Disambig}} a4cebfbf958b2c616c20b32cff79def915b1cb47 0 17 39 2014-02-19T06:15:27Z Kentsmith9 25 Kentsmith9 moved page [[Errors]] to [[Errors (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Errors (disambiguation)]] 1a17e2bdf77cc5b149c74ba90cade54f2e4e20ff 0 24 69 68 2014-02-19T06:16:19Z Kentsmith9 25 Kentsmith9 moved page [[Junction]] to [[Junction (disambiguation)]] wikitext text/x-wiki '''Junction''' may refer to: * Glossary entry for [[Glossary#Junction_or_Junction_Point|Junction]] with definition and images * [[Junction Style Guide]], detailed coverage of different junction types * [[Creating_and_Editing_street_segments#Junctions|Junction]], moving and removal/merging instructions {{Disambig}} 66b219db424f6098c55388ba5abbe88d766af424 0 25 72 2014-02-19T06:16:19Z Kentsmith9 25 Kentsmith9 moved page [[Junction]] to [[Junction (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Junction (disambiguation)]] 141c64e30210244ed3c7bb9e09d48e7f3e969f60 0 30 93 92 2014-02-19T06:16:51Z Kentsmith9 25 Kentsmith9 moved page [[Lock]] to [[Lock (disambiguation)]] wikitext text/x-wiki '''Lock''' may refer to: * [[Editing_ranks#Locked_segments|Locked segments]], how they work and how to unlock them * [[Best map editing practice#Locking Segments|Locking segments]], the best map editing practice * Lock level, setting the security level of a road in the Waze Map Editor [[Map_Editor_Interface_and_Controls#General_Tab|General tab]] * Lock (Landmark), setting on Waze Map Editor when [[Map_Editor_Interface_and_Controls#Tabs_when_a_landmark_is_selected|editing a landmark]] {{Disambig}} 9f3d43838e6e56800188403113a6cfe5e2eaf0ec 94 93 2014-02-21T17:11:57Z Kentsmith9 25 Double redirect fix wikitext text/x-wiki '''Lock''' may refer to: * [[Editing_rank#Locked_segments|Locked segments]], how they work and how to unlock them * [[Best map editing practice#Locking Segments|Locking segments]], the best map editing practice * Lock level, setting the security level of a road in the Waze Map Editor [[Map_Editor_Interface_and_Controls#General_Tab|General tab]] * Lock (Landmark), setting on Waze Map Editor when [[Map_Editor_Interface_and_Controls#Tabs_when_a_landmark_is_selected|editing a landmark]] {{Disambig}} 26f37a231bc41711b85ae71063868d4f2378ad39 0 31 98 2014-02-19T06:16:52Z Kentsmith9 25 Kentsmith9 moved page [[Lock]] to [[Lock (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Lock (disambiguation)]] 4362754670298c189926b6ddc6ad5979c594a5b3 10 35 106 2014-02-19T06:33:47Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Parking''' may refer to: * Parking pin, the marker locating your parked vehicle when [[Nearing destination|nearing your destination]] * Parking lot, the [[Best_map_editing_practice#Parking_Lots|best practices]] for when to map them * Parking lot, the [[Landmarks_by_Type_(US)#Parking_Lot|landmark]] in Waze Map Editor * Parking lot road, the [[Road_Types_(USA)#Parking_Lot_Road|road type]] setting in the Waze Map Editor {{Disambig}} c309a4ce39dbabe9afbaed309c41f9762139b8b1 107 106 2014-02-19T06:34:05Z Kentsmith9 25 Kentsmith9 moved page [[Parking]] to [[Parking (disambiguation)]] wikitext text/x-wiki '''Parking''' may refer to: * Parking pin, the marker locating your parked vehicle when [[Nearing destination|nearing your destination]] * Parking lot, the [[Best_map_editing_practice#Parking_Lots|best practices]] for when to map them * Parking lot, the [[Landmarks_by_Type_(US)#Parking_Lot|landmark]] in Waze Map Editor * Parking lot road, the [[Road_Types_(USA)#Parking_Lot_Road|road type]] setting in the Waze Map Editor {{Disambig}} c309a4ce39dbabe9afbaed309c41f9762139b8b1 108 107 2014-02-19T06:36:33Z Kentsmith9 25 Added Park wikitext text/x-wiki '''Parking''' may refer to: * Parking pin, the marker locating your parked vehicle when [[Nearing destination|nearing your destination]] * Parking lot, the [[Best_map_editing_practice#Parking_Lots|best practices]] for when to map them * Parking lot, the [[Landmarks_by_Type_(US)#Parking_Lot|landmark]] in Waze Map Editor * Parking lot road, the [[Road_Types_(USA)#Parking_Lot_Road|road type]] setting in the Waze Map Editor See also: * Park, landmarks indicating places for recreation {{Disambig}} 6f242a9c4ff07a3e23d07b3dde73bcadaa21720c 109 108 2014-02-19T06:37:52Z Kentsmith9 25 Sorted list wikitext text/x-wiki '''Parking''' may refer to: * Parking lot, the [[Best_map_editing_practice#Parking_Lots|best practices]] for when to map them * Parking lot, the [[Landmarks_by_Type_(US)#Parking_Lot|landmark]] in Waze Map Editor * Parking lot road, the [[Road_Types_(USA)#Parking_Lot_Road|road type]] setting in the Waze Map Editor * Parking pin, the marker locating your parked vehicle when [[Nearing destination|nearing your destination]] See also: * Park, landmarks indicating places for recreation {{Disambig}} 4de248d67874581b4828e0a11305028159e118bc 10 37 115 2014-02-19T06:34:06Z Kentsmith9 25 Kentsmith9 moved page [[Parking]] to [[Parking (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Parking (disambiguation)]] b3fa800d83168c5acc9016d8a1c9dbd80cf5bf0f 10 36 114 113 2014-02-19T06:37:03Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[Parking (disambiguation)]] b3fa800d83168c5acc9016d8a1c9dbd80cf5bf0f 10 41 135 134 2014-02-19T06:39:29Z Kentsmith9 25 Kentsmith9 moved page [[Restrictions]] to [[Restriction (disambiguation)]] wikitext text/x-wiki '''Restriction''' may refer to: * [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|Turn restrictions]], controlling turns 100% of the time * [[Scheduled restrictions]], controlling traffic flow (turns and segments) for some or all vehicle types * Editing restrictions, controlled by a user's [[Editing ranks|editing rank]] {{Disambig}} 9891e8bef529dabe886ddf5af46e5eb2bfc1e464 136 135 2014-02-21T17:11:37Z Kentsmith9 25 Double redirect fix wikitext text/x-wiki '''Restriction''' may refer to: * [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|Turn restrictions]], controlling turns 100% of the time * [[Scheduled restrictions]], controlling traffic flow (turns and segments) for some or all vehicle types * Editing restrictions, controlled by a user's [[editing rank]] {{Disambig}} 09d9e72c3a6d425004008ecbfafede74a4deadd1 10 42 138 2014-02-19T06:39:29Z Kentsmith9 25 Kentsmith9 moved page [[Restrictions]] to [[Restriction (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Restriction (disambiguation)]] 45cd8a4ca2b07ca8e213440eafbf02b441e42e50 10 44 145 2014-02-19T06:41:43Z Kentsmith9 25 Kentsmith9 moved page [[Search]] to [[Search (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Search (disambiguation)]] f0ce87684654b9f11f7de6561ba53a75a847265e 0 27 82 81 2014-02-19T06:43:13Z Kentsmith9 25 Kentsmith9 moved page [[Level]] to [[Level (disambiguation)]] wikitext text/x-wiki '''Level''' may refer to: * Road level, is actually [[Creating_and_Editing_street_segments#Road_elevation|road elevation]], relative to other roads nearby * Zoom level, the WME [[Map_Editor_Interface_and_Controls#Zoom_Control|Zoom Control]] * Lock level, is actually lock rank, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's rank * Editing level, is actually [[Your_Rank_and_Points#Map_editing_rank|Map Editing Rank]] relative to other editors {{Disambig}} e5b8034e845c8eb23be586ddfd7a39f3998c6653 10 28 85 2014-02-19T06:43:13Z Kentsmith9 25 Kentsmith9 moved page [[Level]] to [[Level (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Level (disambiguation)]] 86b9cc6fd7b58199955f1867412038ae025ffc71 0 20 47 2014-02-19T06:43:54Z Kentsmith9 25 Kentsmith9 moved page [[GPS]] to [[GPS (disambiguation)]] wikitext text/x-wiki #REDIRECT [[GPS (disambiguation)]] 85e3789fc287515a316fee1a648da879ec17fb55 10 59 191 2014-02-19T06:45:11Z Kentsmith9 25 Kentsmith9 moved page [[Zoom]] to [[Zoom (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Zoom (disambiguation)]] a246b0a54bf9a58fea428d7c7bde6442eecd9f8b 0 15 35 2014-02-19T06:45:42Z Kentsmith9 25 Kentsmith9 moved page [[Stop point]] to [[Stop point (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Stop point (disambiguation)]] 2e8f20003e0b91a5e5b54974504fe7b2d438330e 10 46 151 150 2014-02-19T06:45:42Z Kentsmith9 25 Kentsmith9 moved page [[Stop point]] to [[Stop point (disambiguation)]] wikitext text/x-wiki '''Stop point''' may refer to: * Stop point, used with [[House_Numbers_in_WME#Setting_the_Stop_Point|house numbers]] for navigation * Stop point, used in [[How_to_Navigate#Add_a_stop_point|navigation]] to go to multiple destinations in order {{Disambig}} 139c49d806a01e9ebd92a321152d05a04b7978a6 0 32 101 100 2014-02-19T06:46:36Z Kentsmith9 25 Kentsmith9 moved page [[Map updates]] to [[Map updates (disambiguation)]] wikitext text/x-wiki '''Map updates''' may refer to: * Map updates, the total points a Waze editor has displayed on their [[Dashboard#Your_Rank_and_Points|Dashboard]] * Map updates, related to the FAQ question [[FAQ#When_do_my_edits_show_up_in_the_Waze_app.3F|When do my edits show up in the Waze app]] * Map updates, how often the servers are updated through the [[timeline of updating process]] * Map updates, made by users through the [[Waze Map Editor]] It may also refer to: * [[Update Requests in Waze Map Editor]], the balloon icons from user reported map problems * [[Map Problems in Waze Map Editor]], the balloon icons from automated system reports {{Disambig}} 4bed646857c26bcf30dc413c81f177bba4f41634 0 34 105 2014-02-19T06:46:36Z Kentsmith9 25 Kentsmith9 moved page [[Map updates]] to [[Map updates (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Map updates (disambiguation)]] 9d12f9b2c315043459e0ca81dc77af02465a23aa 0 22 59 2014-02-19T06:47:12Z Kentsmith9 25 Kentsmith9 moved page [[Icon]] to [[Icon (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Icon (disambiguation)]] b75b0e54b8face4e25ab0131d9200693e1eb9a40 60 59 2014-02-21T20:15:09Z Kentsmith9 25 Changed to point to primary article with hatnote on page wikitext text/x-wiki #REDIRECT [[Waze Symbols]] 72e857ce1d00b04394a52353e44165df1f9875a9 10 66 11843 11842 2014-02-23T12:59:50Z NetHunter 1 Updated the link to the Israeli wiki wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [https://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul> 40a8b0bd0c28bdb610aa705e6b2738f839fe18e2 11844 11843 2014-03-14T16:01:14Z Kentsmith9 25 Added Turkey wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [https://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Turkey]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> a73309f4023ce54f778b962afe7481eab993b0f3 203 2014-03-15T20:15:06Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[24_hour_format]] 5c82aea022644e46755653ac734892b77444fb22 204 203 2014-03-21T04:34:03Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[24-hour_format]] 617d94034a19a7d33b9b096d46ee4690cc0945ae 10 58 11737 11736 2014-02-24T08:24:56Z Kentsmith9 25 Added a few more icons wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | important = Mbox important.png | warning = mbox_warning_yellow.png | caution = Mbox caution.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | speculation = Mbox speculation.png | construction = Warning blue construction.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table> 938327deaf87dae96760f3393a65c2aab6dea2d5 11738 11737 2014-02-24T08:52:46Z Kentsmith9 25 Resorted list wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox_warning_yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Warning blue construction.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table> de6bf45e6d961ebbeefe7514f211f41e5cc55ec1 11739 11738 2014-02-25T02:10:29Z Kentsmith9 25 Swapped construction image from blue to yellow wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox_warning_yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table> 4be3b392c3aba590dff9b8236c4a5a5066b08dd3 11740 11739 2014-03-02T16:21:22Z Kentsmith9 25 Added Category wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox_warning_yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> [[Category:Missing Template Documentation]] </noinclude> 6a0b4df22c27a59f91c98adb9ca9b6ee06f59e72 11741 11740 2014-03-02T16:22:29Z Kentsmith9 25 Added Category wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox_warning_yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> <!-- This category is only for the template itself --> <!-- Move these to doc subpage once created --> [[Category:Template Management]] [[Category:Missing Template Documentation]] </noinclude> 86eb2b912158d17304b546bbcbd61e0d2359f538 11742 11741 2014-03-02T22:08:07Z Kentsmith9 25 Added documentation wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox_warning_yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> {{Documentation|content=This subtemplate supports the default values of {{tl|Mbox}}. It should not be altered without review from a Wiki Expert. Contact one through the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion forum.]}} <!-- This category is only for the template itself --> [[Category:Template Management]] </noinclude> 897dca0c4ae7987c99441b6f2af325f2f5f88dd2 11743 11742 2014-03-16T21:35:45Z Kentsmith9 25 Moved category wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox_warning_yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> {{Documentation|content=This subtemplate supports the default values of {{tl|Mbox}}. It should not be altered without review from a Wiki Expert. Contact one through the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion forum.]}} <!-- This category is only for the template itself --> [[Category:Template:Mbox]] </noinclude> e2b2942c204592a33d4634043da72ff1ab5f4b3a 0 14 34 33 2014-02-27T05:09:18Z Kentsmith9 25 Moved to redirect wikitext text/x-wiki #REDIRECT [[Glossary#Junction_or_Junction_Point]] bdbc6a77a993613a477373c564e48934c0345b3c 0 96 648 647 2014-03-07T00:56:13Z Kentsmith9 25 Reworded guidance to keep in list form, keeping the additional notation. wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m zoom level. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_rank#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a transition penalty when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] d484b2a8e5dcbc7582f5cf5a9a5dda15e36126a3 649 648 2014-03-07T18:59:14Z Kentsmith9 25 /* {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) */ clarified which 100m level wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high penalty and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_rank#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a transition penalty when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] 7986c230093d34d9d5683a642c421500331897c6 650 649 2014-03-15T22:48:43Z Kentsmith9 25 Wikilinked wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_rank#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing_penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] 0095af9434223dd06c6e4470737838107e29e828 651 650 2014-03-16T06:36:00Z Kentsmith9 25 Added category wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Map Editing (new Editor)|Waze Map Editor]], identify and solve [[Map_Problems_in_Waze_Map_Editor|map problems]] and [[Update_Requests_in_Waze_Map_Editor|update requests]], set standards for [[How_to_label_and_name_roads|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[How to label and name roads#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_Types_(USA)#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_rank#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing_penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Map Editing %28new Editor%29|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] 17d2d60117bbf581e72bca1edd32ea35981c484c 652 651 2014-03-16T07:52:37Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[At-Grade Connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Only mark segments as toll roads if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[At-Grade Connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_rank#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a parking lot serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: * Main entrances from the roads outside the parking lot * Lanes that run along storefronts * Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) * Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/> [[Image:ParkingLotRoad_ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction_Style_Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing_penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 34eb38d62a57fc8dc1739cb27faadafe866c2f76 0 73 284 283 2014-03-07T07:50:19Z Kentsmith9 25 fixed link wikitext text/x-wiki #REDIRECT [[Abbreviations and acronyms]] 474590d763e7e7bda332a8deb4d6c7a2b9529e13 0 29 87 86 2014-03-07T07:53:19Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[Level (disambiguation)]] 86b9cc6fd7b58199955f1867412038ae025ffc71 10 40 130 129 2014-03-07T07:53:59Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki '''Rank''' may refer to: * Lock rank, the security setting on [[FAQ#What_is_a_locked_road.3F|locked roads]] preventing alteration by editors below the road's rank * [[Your_Rank_and_Points#Map_editing_rank|Map Editing Rank]] relative to other editors See also: [[Level (disambiguation)]] {{Disambig}} 2fbf86bd0a490e7980c73b47ac138eb9f6537ab9 10 48 157 156 2014-03-07T08:46:11Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[Stop point (disambiguation)]] 2e8f20003e0b91a5e5b54974504fe7b2d438330e 10 47 155 154 2014-03-07T08:46:25Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[Stop point (disambiguation)]] 2e8f20003e0b91a5e5b54974504fe7b2d438330e 10 49 159 158 2014-03-07T08:46:43Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[Stop point (disambiguation)]] 2e8f20003e0b91a5e5b54974504fe7b2d438330e 10 38 120 119 2014-03-07T08:47:27Z Kentsmith9 25 Double redirect fix wikitext text/x-wiki '''Points''' typically refer to: * [[Your_Rank_and_Points|Points]], the collection and counting of credits related to Waze usage and editing * Points, the elements often confused with [[nodes]] See also: * [[Junction point]] * [[Stop point (disambiguation)|Stop point]] {{Disambig}} 3ecb0fe60cd1f8d837ac21f27a45c0665fbb260a 0 12 30 29 2014-03-07T08:48:01Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki '''Editing points''' typically refer to: * [[Your_Rank_and_Points|Editing points]], the collection and counting of credits related to Waze usage and editing * Editing points, making changes to the elements often confused with [[nodes]] See also: * [[Junction point]] * [[Stop point (disambiguation)|Stop point]] {{Disambig}} 2c28faac87241c3e19e62a959d94be15e3a49b20 0 33 104 103 2014-03-09T06:26:11Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[Map updates (disambiguation)]] 9d12f9b2c315043459e0ca81dc77af02465a23aa 10 28 11356 11355 2014-03-14T16:03:26Z Kentsmith9 25 Added Turkey wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> [[Image:Sq.png]]&nbsp;[[Albania|Shqipëria (Albania)]] [[Image:Ar.png]]&nbsp;[[Argentina]] [[Image:Au.png]]&nbsp;[[Australia]] [[Image:Be.png]]&nbsp;[[Belgium]] [[Image:Br.png]]&nbsp;[[Brasil]] [[Image:Bg.png]]&nbsp;[[България|България (Bulgaria)]] [[Image:Ca.png]]&nbsp;[[Canada]] [[Image:Cn.png]]&nbsp;[[中国|中国 (China)]] [[Image:Co.png]]&nbsp;[[Colombia]] [[Image:Cr.png]]&nbsp;[[Costa Rica]] [[Image:Cy.png]]&nbsp;[[Cyprus]] [[Image:Cz.png]]&nbsp;[[Czech]] [[Image:Dk.png]]&nbsp;[[Denmark]] [[Image:De.png]]&nbsp;[[Deutschland]] [[Image:Ee.png]]&nbsp;[[Eesti|Eesti (Estonia)]] [[Image:Es.png]]&nbsp;[[España|España (Spain)]] [[Image:Fi.jpg]]&nbsp;[[Finland]] [[Image:Fr.png]]&nbsp;[[France]] [[Image:Ie.png]]&nbsp;[[Ireland]] [[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] [[Image:India1.jpg]]&nbsp;[[India]] [[Image:In.png]]&nbsp;[[Indonesia]] [[Image:It.png]]&nbsp;[[Italy]] [[Image:Korea-flag.png||25px]]&nbsp;[[Korea|대한민국 (Korea)]] [[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|日本 (Japan)]] [[Image:Kv.png]]&nbsp;[[Kosovo]] [[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] [[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] [[Image:Lux.gif]]&nbsp;[[Luxembourg|Lëtzebuerg (Luxembourg)]] [[Image:Hu.png]]&nbsp;[[Hungary|Magyarország (Hungary)]] [[Image:My.jpg]]&nbsp;[[Malaysia]] [[Image:Mx.gif|25px]]&nbsp;[[México]] [[Image:Nl.png]]&nbsp;[[Nederland]] [[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] [[Image:Oesterreich.png]]&nbsp;[[Österreich|Österreich (Austria)]] [[Image:Pl.png]]&nbsp;[[Poland]] [[Image:Pt.png]]&nbsp;[[Portugal]] [[Image:Ro.png]]&nbsp;[[Romania]] [[Image:Ru.png]]&nbsp;[[Russia]] [[Image:SRb.png]]&nbsp;[[Serbia]] [[Image:Sk.png]]&nbsp;[[Slovakia]] [[Image:SI.png]]&nbsp;[[Slovenia]] [[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] [[Image:Se.png]]&nbsp;[[Sweden]] [[Image:Swiss1.png]]&nbsp;[[Switzerland]] [[Image:Turkey.png]]&nbsp;[[Turkey]] [[Image:Ua.jpg]]&nbsp;[[Ukraine]] [[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] [[Image:Us.png]]&nbsp;[[USA]] ----<!-- --><noinclude>[[Category:Country list]]</noinclude> 690b3ec6e9caf391fcb9f233f79a4dcbeabbb1db 11357 11356 2014-03-18T05:28:46Z Kentsmith9 25 converted to bullets wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mx.gif|25px]]&nbsp;[[México]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Turkey]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> c45f0633e1a1b97399cffc4a9d36555a82a5fc68 11358 11357 2014-03-19T08:27:27Z Kentsmith9 25 Updated mexico flas wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Turkey]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> 6a88805d5dcacc40dc86fa04e0810f940d12e8cc 10 36 11462 11461 2014-03-14T21:19:36Z Kentsmith9 25 Expanded anchor support wikitext text/x-wiki {{#if:{{{1|}}}|<span id="{{{1|}}}"></span>}}<!-- -->{{#if:{{{2|}}}|<span id="{{{2|}}}"></span>}}<!-- -->{{#if:{{{3|}}}|<span id="{{{3|}}}"></span>}}<!-- -->{{#if:{{{4|}}}|<span id="{{{4|}}}"></span>}}<!-- -->{{#if:{{{5|}}}|<span id="{{{5|}}}"></span>}}<!-- -->{{#if:{{{6|}}}|<span id="{{{6|}}}"></span>}}<!-- -->{{#if:{{{7|}}}|<span id="{{{7|}}}"></span>}}<!-- -->{{#if:{{{8|}}}|<span id="{{{8|}}}"></span>}}<!-- -->{{#if:{{{9|}}}|<span id="{{{9|}}}"></span>}}<!-- -->{{#if:{{{10|}}}|<span id="{{{10|}}}"></span>}}<!-- -->{{#if:{{{11|}}}|<span class="error">Error in [[Template:Anchor]]: too many anchors, maximum is 10.</span>}}<noinclude> {{Documentation}} <!-- PLEASE ADD CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --> </noinclude> 07e11cee92129ba0f450efd7e0e28c94fb968cbb 0 18 40 2014-03-15T00:20:51Z Kentsmith9 25 Created redirect wikitext text/x-wiki #REDIRECT [[WME_errors]] a97cf57214cfe5c4cc83363441f6dd1d00143f16 10 60 192 2014-03-15T17:48:55Z Kentsmith9 25 Created transcludable page wikitext text/x-wiki In a [http://en.wikipedia.org/wiki/24-hour_clock 24-hour format], time is represented with unique hours of the day that do not require the AM and PM indicators. To convert from 12-hour time to 24-hour time, use the following table: {| class="wikitable" style="margin: 1em auto 1em auto;" |- ! align="left" | 12-hour time !! 24-hour time !! Converting the Hour<br/>from 12 to 24 hour time |- | align="left" | 12:00 AM (midnight) - 12:59 AM | align="left" | 0:00 - 0:59 | align="left" | Use 0 for hour. |- | align="left" | 1:00 AM - 11:59 AM | align="left" | 1:00 - 11:59 | rowspan="2" align="left" | Do nothing. |- | align="left" | 12:00 PM (noon) - 12:59 PM | align="left" | 12:00 - 12:59 |- | align="left" | 1:00 PM - 11:59 PM | align="left" | 13:00 - 23:59 | align="left" | Add 12 to hour. |} The minutes remain the same between the two formats.<noinclude> [[Category:Transcludable pages]] </noinclude> f736d14ec08f2403943e48116afe5779caab9103 193 192 2014-03-21T04:32:38Z Kentsmith9 25 Kentsmith9 moved page [[24 hour format]] to [[24-hour format]] over redirect: Corrected spelling wikitext text/x-wiki In a [http://en.wikipedia.org/wiki/24-hour_clock 24-hour format], time is represented with unique hours of the day that do not require the AM and PM indicators. To convert from 12-hour time to 24-hour time, use the following table: {| class="wikitable" style="margin: 1em auto 1em auto;" |- ! align="left" | 12-hour time !! 24-hour time !! Converting the Hour<br/>from 12 to 24 hour time |- | align="left" | 12:00 AM (midnight) - 12:59 AM | align="left" | 0:00 - 0:59 | align="left" | Use 0 for hour. |- | align="left" | 1:00 AM - 11:59 AM | align="left" | 1:00 - 11:59 | rowspan="2" align="left" | Do nothing. |- | align="left" | 12:00 PM (noon) - 12:59 PM | align="left" | 12:00 - 12:59 |- | align="left" | 1:00 PM - 11:59 PM | align="left" | 13:00 - 23:59 | align="left" | Add 12 to hour. |} The minutes remain the same between the two formats.<noinclude> [[Category:Transcludable pages]] </noinclude> f736d14ec08f2403943e48116afe5779caab9103 0 61 194 2014-03-15T20:14:42Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[24_hour_format]] 5c82aea022644e46755653ac734892b77444fb22 195 194 2014-03-21T04:33:42Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[24-hour_format]] 617d94034a19a7d33b9b096d46ee4690cc0945ae 10 64 200 2014-03-15T20:14:58Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[24_hour_format]] 5c82aea022644e46755653ac734892b77444fb22 201 200 2014-03-21T04:33:53Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[24-hour_format]] 617d94034a19a7d33b9b096d46ee4690cc0945ae 0 63 198 2014-03-15T20:21:20Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[24_hour_format]] 5c82aea022644e46755653ac734892b77444fb22 199 198 2014-03-21T04:34:15Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[24-hour_format]] 617d94034a19a7d33b9b096d46ee4690cc0945ae 0 62 196 2014-03-15T20:21:41Z Kentsmith9 25 Created Redirect wikitext text/x-wiki #REDIRECT [[24_hour_format]] 5c82aea022644e46755653ac734892b77444fb22 0 24 11225 2014-03-16T07:05:55Z Kentsmith9 25 Kentsmith9 moved page [[How to label and name roads]] to [[Road types and names]]: Preparing for subpages wikitext text/x-wiki #REDIRECT [[Road types and names]] 700adfe90ad01be478231919a3cf13bef309e5f5 0 78 421 420 2014-03-17T07:27:22Z Kentsmith9 25 Added category wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] [[Category:Style Guides]] e99c62f6d5e6d0ebe2431cc325300fbb904d51f9 422 421 2014-03-17T07:27:57Z Kentsmith9 25 added category wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] [[Category:Style Guides]] [[Waze Map Editor]] da94634ec5cd2c5ece06b8dd63780651b04a85e6 423 422 2014-03-17T07:29:41Z Kentsmith9 25 Typo wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] [[Category:Style Guides]] [[Category:Waze Map Editor]] 196dbb7893587c0b521d035289c6afaad6225eea 424 423 2014-03-17T08:12:08Z Kentsmith9 25 /* Connector is a signed, numbered exit */ added info on why it needs to be a ramp wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === [[File:GSP_10.jpg|right|border]] '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. In order to receive an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction for Exit Right]] rather than Keep Right or Turn Right, this connecter needs to be a ramp. {{clear}} {|style="margin: 0 auto;" |- valign="top" | [[File:GSP_10A.jpg|x162px]] | [[File:GSP_10B.jpg|x162px]] | Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). |} [[Category:Style Guides]] [[Category:Waze Map Editor]] 1a90a247c179901bef6db06a9a8e4e434d3ea640 426 425 2014-03-19T07:07:43Z Kentsmith9 25 Kentsmith9 moved page [[At-Grade Connectors]] to [[At-grade connectors]]: Sentence case page name wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === [[File:GSP_10.jpg|right|border]] '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. In order to receive an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction for Exit Right]] rather than Keep Right or Turn Right, this connector needs to be a ramp. {{clear}} {|style="margin: 0 auto;" |- valign="top" | [[File:GSP_10A.jpg|x162px]] | [[File:GSP_10B.jpg|x162px]] | Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). |} [[Category:Style Guides]] [[Category:Waze Map Editor]] 8ea18630d4c9daec7ee036393a8186a3404e9722 427 426 2014-03-19T07:09:06Z Kentsmith9 25 added category wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road_Types_(USA)#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == How to label the connector type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == How to name the connector == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == Geometry of the connector == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == Turn restrictions necessary for proper connector routing == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === [[File:GSP_10.jpg|right|border]] '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. In order to receive an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction for Exit Right]] rather than Keep Right or Turn Right, this connector needs to be a ramp. {{clear}} {|style="margin: 0 auto;" |- valign="top" | [[File:GSP_10A.jpg|x162px]] | [[File:GSP_10B.jpg|x162px]] | Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). |} [[Category:Style Guides]] [[Category:Waze Map Editor]] [[Category:Update what links here]] 6c8a07ad36bdc90674100b2b08a3a167ddeab0e3 431 430 2014-03-20T15:58:17Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road types/USA#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == {{anchor|How to label the connector type}} Road type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == {{anchor|How to name the connector}} Road name == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == {{anchor|Geometry of the connector}} Geometry == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == {{anchor|Turn restrictions necessary for proper connector routing}} Turn restrictions == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == === Connector is a signed, numbered exit === [[File:GSP_10.jpg|right|border]] '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. In order to receive an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction for Exit Right]] rather than Keep Right or Turn Right, this connector needs to be a ramp. {{clear}} {|style="margin: 0 auto;" |- valign="top" | [[File:GSP_10A.jpg|x162px]] | [[File:GSP_10B.jpg|x162px]] | Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). |} [[Category:Style Guides]] [[Category:Waze Map Editor]] [[Category:Update what links here]] 159bc9fcb959be864aecaf281ee84a9f699cec55 0 83 450 2014-03-19T07:07:44Z Kentsmith9 25 Kentsmith9 moved page [[At-Grade Connectors]] to [[At-grade connectors]]: Sentence case page name wikitext text/x-wiki #REDIRECT [[At-grade connectors]] ab3b6948181044fa744a649a6c19fb9ed29c5735 10 65 202 2014-03-21T04:32:38Z Kentsmith9 25 Kentsmith9 moved page [[24 hour format]] to [[24-hour format]] over redirect: Corrected spelling wikitext text/x-wiki #REDIRECT [[24-hour format]] 9195d521be6d24c3e9915b9fca4a603e9777d3e5 0 62 197 196 2014-03-21T04:34:26Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[24-hour_format]] 617d94034a19a7d33b9b096d46ee4690cc0945ae 0 27 11271 11270 2014-03-21T07:06:45Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[Technical links]] b3a6c6293804cd9a6b767cfc6d2e166cfdc6b5e0 0 1 4816 1 2014-03-21T07:08:29Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki {{Template:UserMaintainedTop}} {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{:Technical links}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} 05c13700821b96ead507c550ab22fd657c49516c 4820 1 2014-04-23T05:46:56Z Kentsmith9 25 Reverted edits by [[Special:Contributions/Asd|Asd]] ([[User talk:Asd|talk]]) to last revision by [[User:Kentsmith9|Kentsmith9]] wikitext text/x-wiki {{Template:UserMaintainedTop}} {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{:Technical links}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} 05c13700821b96ead507c550ab22fd657c49516c 4822 1 2014-04-27T17:56:58Z Kentsmith9 25 Reverted edits by [[Special:Contributions/EduardoCarvajal|EduardoCarvajal]] ([[User talk:EduardoCarvajal|talk]]) to last revision by [[User:Kentsmith9|Kentsmith9]] wikitext text/x-wiki {{Template:UserMaintainedTop}} {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{:Technical links}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} 05c13700821b96ead507c550ab22fd657c49516c 4823 1 2014-04-27T17:59:24Z Kentsmith9 25 Added LatinAmerica page link from last revision temporarily until we have translation working wikitext text/x-wiki {{Template:UserMaintainedTop}} <p style="text-align: right;"><span style="font-size:smaller;">Change Language: '''English''',[[Latinoamerica|Español]]</span></p> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{:Technical links}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} b2b70f0acb8d733f68d6e7f34a57a83597a6d318 4824 1 2014-04-29T23:41:20Z Kentsmith9 25 Protected "[[Main Page]]": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki {{Template:UserMaintainedTop}} <p style="text-align: right;"><span style="font-size:smaller;">Change Language: '''English''',[[Latinoamerica|Español]]</span></p> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{:Technical links}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} b2b70f0acb8d733f68d6e7f34a57a83597a6d318 4825 1 2014-05-22T18:26:08Z Kentsmith9 25 missing space wikitext text/x-wiki {{Template:UserMaintainedTop}} <p style="text-align: right;"><span style="font-size:smaller;">Change Language: '''English''', [[Latinoamerica|Español]]</span></p> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Check the server status and major service issues] |} <div style="font-size:smaller"> <div style="font-size:smaller;width:20%;float:right;margin:0;border:solid lightblue;background:#fffff0;padding:2px"> <p style="margin:0;padding:2px;background:lightblue;border:thin solid lightblue;font-weight:bold"> Waze for your country</p> For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{CountriesList}} <div style="font-size:smaller"> {{Languages and Countries}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> About Waze</p> <div style="padding:5px"> {{About Waze}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Getting started</p> <div style="padding:5px"> {{Getting Started}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> You can make Waze even better</p> <div style="padding:5px"> {{How You Can Help}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Problems, bugs and limitations</p> <div style="padding:5px"> {{Problems, bugs and limitations}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Development plans and priorities</p> <div style="padding:5px"> {{Development plans and priorities}} </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:150%"> Technical information</p> <div style="padding:5px"> {{:Technical links}} </div></div> </div> <br clear=all> <p style="font-size:xx-large;font:bold">Have fun going your own Waze</p> [[Image:Wazewordcloud.PNG]] {{UserMaintained}} 9184bada538fb5788e0468052e7467ac1581b86d 0 21 53 52 2014-03-25T03:46:15Z Kentsmith9 25 added turn icons wikitext text/x-wiki '''Icon''' links directly to: * [[Waze symbols]], client app icons for alert, moods (other drivers), ranks, and candy '''Icon''' may also refer to: * Forum icon, (or [[Your_Rank_and_Points#Forum_badges|Forum badge]]) appears in right pane of an editor's forum post * Park icon, (or [[Nearing_destination|parking pin]] to mark the location of your vehicle * [[Map_Editing_Quick-start_Guide#Turn icons|Turn icon]], the turn indicators in the Waze Map Editor {{Disambig}} 863378fa1a7deba519dd7dcf41253a5bd05b2440 0 89 477 476 2014-03-28T18:19:20Z Kentsmith9 25 Removed sortability to clean up display; clarified table data a bit more wikitext text/x-wiki Waze uses at least three different banks of servers geo-located for best performance globally. When panning around the [http://www.waze.com/livemap|Waze livemap], the system automatically switches to the server infrastructure for the area you are viewing. The Waze Map Editor does not switch automatically. You need to use the infrastructure selector menu, found at the top-right corner of the page. This menu is not visible in full-screen mode, so if your [[Map Editor Interface and Controls#Map_Editor_Tool_Bar|editor toolbar]] is all the way at the top of the screen, use Shift+F to get out of full-screen mode. The WME Permalink also contains a switch for the current server infrastructure onscreen, but it is not yet functional. The current Permalink URL values are: {| class="wikitable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! URL Value |- | USA & Canada | &amp;env=usa |- | Rest of the World | &env=row |- | Israel | &env=il |} For example, the URL for Johannesburg, South Africa is: :<nowiki>https://www.waze.com/editor/?zoom=3&lat=-26.19321&lon=28.04383</nowiki>'''&env=row''' NOTE: The servers in Israel are being migrated to the World servers and will eventually be taken down. == Overview == All maps for each region listed above are separate. Anything reported or created on one of these servers will not be visible on the others. Note that you do have a login automatically created on the different servers, so you can mistakenly log into the wrong server and not realize it until you look for your points, groups or prior map changes. You may find map changes in one server for an area covered by another. This might make you think you are on the right server, but that area is not kept in sync with the primary server. At this time that area is not used by the client app and serves no purpose so do not bother making any changes to it. If you visit http://www.waze.com , it should automatically switch you to the correct server. In case the server does not correctly forward you to the right server (for example [[Dashboard]] or [http://www.waze.com/editor Waze Map Editor]] is not showing the correct amount of points or routes), use one of the links above. == Fixing server link for client application == If the client application jumps to the wrong server by mistake (it has happened to a few people in the past) you might not be able to see your points. If you take your mobile phone or smart device from the US to Europe or vis-a-versa, you may need to force the client to switch to an alternate server. In both of the above cases, start the Waze application on the client and try to login with your local account. If this fails: * Login with a temporary account (by clicking skip button from the Sign Up menu) * Go to Navigate from the main menu and from the '''search for address bar''' enter one of the following character sequences to move the the server for your area {| class="wikitable sortable" style="background:none; font-size:100%; margin: 1em auto 1em auto" border="1" |- align="center" ! Area of World ! Search for |- | USA & Canada | <nowiki>##@usa</nowiki> |- | Rest of the World | <nowiki>##@other</nowiki> |- | Israel | <nowiki>##@il</nowiki> |} * Restart the application and enter your original login information 04d6576809d5a606a8b8623a77c7a9af302c0b30 10 66 11845 11844 2014-03-28T18:30:12Z Kentsmith9 25 Added Norway wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [https://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Turkey]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> d6190cb8228096aeab5b059a56ecc578fcd7580a 11849 11848 2014-05-31T22:09:50Z Kentsmith9 25 Consistent formatting at 25px wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [https://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Turkey]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 368f06416ddcd4acc601822426a30acdc434e149 11850 11849 2014-06-17T07:37:46Z Kentsmith9 25 Fixed link wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Turkey]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 4da6a07a4246e9bf67891994b4f505a26c20316b 10 28 11359 11358 2014-03-28T18:30:58Z Kentsmith9 25 Added Norway wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Norway_flag.png]]&nbsp;[[Norway]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Turkey]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> 1547137c4e7ffb5663a15c2bfdde04432a91660d 11363 11362 2014-05-31T22:10:58Z Kentsmith9 25 Keeping consistent formatting at 25px wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Na.png|25px]]&nbsp;[[Namibia]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Norway_flag.png]]&nbsp;[[Norway]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Turkey]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> 54ca66d174ad4ab1096c3acb138bb7bc19d8338e 0 13 10781 10780 2014-03-31T12:47:53Z BellHouse 29 Entzug des AM-Gebiets nach 90 Tagen Inaktivität ergänzt wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Was macht ein Area-Manager= Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. Er besitzt die [[Rechte zum Bearbeiten der Karte|Rechte]], um alle nötigen Arbeiten auszuführen. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Im August 2012 sind die Rechte, um an der Karte zu arbeiten angepasst worden. Der Area-Manager kann nun nur noch Straßen bearbeiten, für die er den notwendigen Level besitzt. Alle Straßen können vom AM nur noch bearbeitet werden, wenn sie nicht von einem Editor mit höherem Level gelockt wurden. '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Hilfestellung leisten an die Editoren in seiner Gegend. * Allgemein sollte man immer sein betreutes Gebiet im Auge behalten. '''Wichtige arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. =Anmeldung Area-Manager= Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:'''<br> * Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. * Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. * Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. * Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. * Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. * Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". * Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. * Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *TSWA(AT) *GPSRitter(AT) *Caradellino(AT) *argus-cronos(CH) *svx-biker(CH) *pikifoo(CH) =Richtlinien, die Du genau kennen solltest!= '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' '''Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden.''' '''Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes.''' '''Wir dulden keinen Vandalismus!''' =Bleibe als Area Manager aktiv= Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. =Online-Formular= Folgendes musst Du tun: * Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. * Klicke auf [[WME_Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. * Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. * Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. Bist Du Areamanager geworden, dann trage dich hier auf der [https://docs.google.com/spreadsheet/lv?hl=en_GB&hl=en_GB&key=0AnK4ogNrUnhmdDM1LXIzNXNFblJMMkJRelo0NzR5dkE&type=view&gid=0&f=true&colid0=3&filterstr0=UK&sortcolid=-1&sortasc=true&rowsperpage=250 Liste] ein. Und hier darfst Du auch dein [https://maps.google.com/maps?q=http://maps.google.com/maps/ms%3Fie%3DUTF8%26hl%3Den%26oe%3DUTF8%26vps%3D2%26authuser%3D0%26msa%3D0%26output%3Dkml%26msid%3D202201394911137948753.0004b7bda319bcdaa2c8b&hl=en&sll=36.244273,-95.712891&sspn=37.932189,86.572266&t=m&z=2 Gebiet] einzeichnen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 6792c740e90acd69cef17f289c593cda12158a66 10782 10781 2014-04-01T08:07:31Z BellHouse 29 Reihenfolge der Abschnitte, Link zu alter defekter AM-Liste entfernt wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. Er besitzt die [[Rechte zum Bearbeiten der Karte|Rechte]], um alle nötigen Arbeiten auszuführen. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Im August 2012 sind die Rechte, um an der Karte zu arbeiten angepasst worden. Der Area-Manager kann nun nur noch Straßen bearbeiten, für die er den notwendigen Level besitzt. Alle Straßen können vom AM nur noch bearbeitet werden, wenn sie nicht von einem Editor mit höherem Level gelockt wurden. '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Hilfestellung leisten an die Editoren in seiner Gegend. * Allgemein sollte man immer sein betreutes Gebiet im Auge behalten. '''Wichtige arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. ==Anmeldung Area-Manager== Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:'''<br> * Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. * Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. * Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. * Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. * Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. * Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". * Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. * Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *TSWA(AT) *GPSRitter(AT) *Caradellino(AT) *argus-cronos(CH) *svx-biker(CH) *pikifoo(CH) ===Richtlinien, die Du genau kennen solltest!=== '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. ===Online-Formular=== Folgendes musst Du tun: * Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. * Klicke auf [[WME_Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. * Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. * Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 8450f3d84ce039c7163a3c9ff51f351b1cafb2c7 10783 10782 2014-04-01T08:28:52Z BellHouse 29 AM-Liste D wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. Er besitzt die [[Rechte zum Bearbeiten der Karte|Rechte]], um alle nötigen Arbeiten auszuführen. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Im August 2012 sind die Rechte, um an der Karte zu arbeiten angepasst worden. Der Area-Manager kann nun nur noch Straßen bearbeiten, für die er den notwendigen Level besitzt. Alle Straßen können vom AM nur noch bearbeitet werden, wenn sie nicht von einem Editor mit höherem Level gelockt wurden. '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Hilfestellung leisten an die Editoren in seiner Gegend. * Allgemein sollte man immer sein betreutes Gebiet im Auge behalten. '''Wichtige arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. ==Anmeldung Area-Manager== Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:'''<br> * Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. * Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. * Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. * Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. * Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. * Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". * Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. * Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *TSWA(AT) *GPSRitter(AT) *Caradellino(AT) *argus-cronos(CH) *svx-biker(CH) *pikifoo(CH) ===Richtlinien, die Du genau kennen solltest!=== '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. ===Online-Formular=== Folgendes musst Du tun: * Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. * Klicke auf [[WME_Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. * Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. * Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich * Schweiz ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 3e69a3d8b4c57f52c64b1cea1552289885dcf56a 10784 10783 2014-04-01T08:33:31Z BellHouse 29 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. Er besitzt die [[Rechte zum Bearbeiten der Karte|Rechte]], um alle nötigen Arbeiten auszuführen. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Im August 2012 sind die Rechte, um an der Karte zu arbeiten angepasst worden. Der Area-Manager kann nun nur noch Straßen bearbeiten, für die er den notwendigen Level besitzt. Alle Straßen können vom AM nur noch bearbeitet werden, wenn sie nicht von einem Editor mit höherem Level gelockt wurden. '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Hilfestellung leisten an die Editoren in seiner Gegend. * Allgemein sollte man immer sein betreutes Gebiet im Auge behalten. '''Wichtige arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. ==Anmeldung Area-Manager== Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:'''<br> * Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. * Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. * Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. * Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. * Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. * Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". * Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. * Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *TSWA(AT) *GPSRitter(AT) *Caradellino(AT) *argus-cronos(CH) *svx-biker(CH) *pikifoo(CH) ===Richtlinien, die Du genau kennen solltest!=== '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. ===Online-Formular=== Folgendes musst Du tun: * Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. * Klicke auf [[WME_Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. * Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. * Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt) * Schweiz (kommt) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 3cfc66282c53bc43e4e7aec1c4e093e6348f6d44 10785 10784 2014-04-01T08:34:51Z BellHouse 29 "kommt bald" an AM-Listen AT und CH wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. Er besitzt die [[Rechte zum Bearbeiten der Karte|Rechte]], um alle nötigen Arbeiten auszuführen. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Im August 2012 sind die Rechte, um an der Karte zu arbeiten angepasst worden. Der Area-Manager kann nun nur noch Straßen bearbeiten, für die er den notwendigen Level besitzt. Alle Straßen können vom AM nur noch bearbeitet werden, wenn sie nicht von einem Editor mit höherem Level gelockt wurden. '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Hilfestellung leisten an die Editoren in seiner Gegend. * Allgemein sollte man immer sein betreutes Gebiet im Auge behalten. '''Wichtige arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. ==Anmeldung Area-Manager== Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:'''<br> * Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. * Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. * Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. * Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. * Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. * Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". * Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. * Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *TSWA(AT) *GPSRitter(AT) *Caradellino(AT) *argus-cronos(CH) *svx-biker(CH) *pikifoo(CH) ===Richtlinien, die Du genau kennen solltest!=== '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. ===Online-Formular=== Folgendes musst Du tun: * Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. * Klicke auf [[WME_Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. * Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. * Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt bald) * Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 0c94827a83ead4e37538785f355aba4f18d4f6d4 10786 10785 2014-04-01T13:30:22Z BellHouse 29 /* Was macht ein Area-Manager */ Beschreibung Rechte des AM aktualisiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Den Editoren seiner Gegend Hilfestellung leisten. * Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. ==Anmeldung Area-Manager== Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:'''<br> * Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. * Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. * Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. * Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. * Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. * Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". * Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. * Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *TSWA(AT) *GPSRitter(AT) *Caradellino(AT) *argus-cronos(CH) *svx-biker(CH) *pikifoo(CH) ===Richtlinien, die Du genau kennen solltest!=== '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. ===Online-Formular=== Folgendes musst Du tun: * Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. * Klicke auf [[WME_Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. * Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. * Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt bald) * Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] b4ac8a1054055ebc7c249d31b42e7d0f360afc97 10787 10786 2014-05-19T09:26:23Z BellHouse 29 BellHouse als AMS D ergänzt wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Den Editoren seiner Gegend Hilfestellung leisten. * Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. == Anmeldung Area-Manager == Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:''' *Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. *Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. *Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. *Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. *Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. *Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". *Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. *Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *Caradellino (AT) *argus-cronos (CH) *svx-biker (CH) *pikifoo (CH) === Richtlinien, die Du genau kennen solltest! === '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. === Online-Formular === Folgendes musst Du tun: *Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. *Klicke auf [[WME Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. *Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. *Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt bald) * Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] cce9412a98abfe2fb029822f0b46c909a00638ea 0 5 10364 10363 2014-04-11T10:01:03Z BellHouse 29 Layout aktualisiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] == Einleitung == Wie Waze selbst ist diese Seite durch die Gemeinschaft entstanden und entwickelt sich kontinuierlich weiter. Viele hilfreiche Seiten existieren bereits unter [[Der Area Manager]], wie man den [[Der Waze Map-Editor|Karteneditor]] benutzt, Kartenfehler identifiziert und bearbeitet, Standards um Straßen zu klassifizieren und zu benennen und eine Seite über [[Häufig gestellte Fragen]]. Der Zweck dieser Seite ist es, Area-Managern und allen Benutzern zu helfen, eine Karte zu erstellen, welche für alle Waze-Endbenutzer während der Fahrt gut funktioniert. Auch kann so Mehraufwand durch nochmaliges Bearbeiten auf Grund von Fehlern oder Beschränkungen der Waze-Applikation vermieden werden. == Anleitungen == Im Wiki finden sich zahlreiche Anleitungen. Das Wichtigste am Anfang ist daher, sich mit den Anleitungen auseinanderzusetzen. Also lies die [[Anleitung zum Bearbeiten der Karte]] sorgfältig, bevor Du die Karte bearbeitest. == Hauptziele == === Benutzerfreundlichkeit === Wenn es um die Karte geht, ist das oberste Gebot: Für den Waze-Benutzer eine einfache Karte zu erstellen, der einfach zu folgen ist auf dem kleinen Bildschirm. Die Anweisungen sollen klar und sinnvoll sein und nur dann erscheinen, wenn sie auch gebraucht werden. === Einfachheit === Es soll nicht jede einzelne Spur auf der Karte eingezeichnet werden. Dies führt häufig nur zu unnötiger Komplexität, unlogischen Anweisungen beim Navigieren sowie unübersichtlichen Verhältnissen auf der Karte und schlussendlich zu unnötiger Mehrarbeit beim Korrigieren. === Erhaltung des bestehenden Zustandes === Durch das Befahren der Straßen werden in den Segmenten Informationen gespeichert, wie z.B. die Geschwindigkeit, welche für das optimale Routing benötigt wird. Wenn ein Segment gelöscht wird, gehen diese Informationen verloren. Wenn an einem unübersichtlichen Gewirr von Segmenten gearbeitet wird, ist es die bessere Wahl, diese weiterzuverwenden, anstatt bestehende zu löschen und neu zu zeichnen. === End-Kreuzung === Damit Waze aus einer Sackgasse herausnavigieren kann ist eine [[Erstellen und bearbeiten eines Segments#Kreuzung am Ende einer Sackgasse|End-Kreuzung]] zwingend nötig. Jedes Segment auf der Waze-Karte besitzt eine End-Kreuzung oder ist durch Kreuzungen mit anderen Segmenten verbunden. Dies ist die '''Goldene Regel'''. Dies gilt für alle Sackgassen und Segmente, die allein auf der Karte daliegen und nicht mit anderen Segmenten verbunden sind. Dies gilt auch für alle Straßentypen. Der Karteneditor fügt die Kreuzungen mittlerweile selbstständig hinzu. Solltest Du dennoch Straßen ohne End-Kreuzung vorfinden, füge sie bitte manuell hinzu. == In der Praxis == === In zwei Einbahnstraßen aufteilen oder nicht? === Es ist selten eine gute Idee, eine Straße, die nur durch Ein- und Ausfahrten auf eine Autobahn oder Hauptverkehrsstraße verbunden ist, in zwei Einbahnen aufzuteilen. An einer Kreuzung müssen auch nicht die Einmündungen aufgeteilt werden. Kreuzungen werden dadurch unnötig kompliziert, auf dem Bildschirm ist nichts mehr richtig zu erkennen, und die Anweisungen bei der Navigation sind verwirrend oder unsinnig. <br/>'''Eine Straße sollte in zwei Einbahnen aufgeteilt werden wenn:''' *Mindestens 5 Meter Abstand zwischen den Fahrspuren besteht. (Abgetrennt durch Beton, Blumentöpfe oder Beete, Bäume oder Grasflächen.) *Die GPS-Punkte liegen bei einer Zoomstufe von 100 Metern im Karteneditor genügend weit auseinander. <br/>'''Eine Straße sollte nicht in zwei Einbahnen aufgeteilt werden wenn:''' *Eine nicht befahrbare Fläche von weniger als 5 Metern zwischen den Fahrspuren besteht. *Eine längere Abbiegespur zwischen beiden Fahrtrichtungen existiert. *Viele Straßen kreuzen, die nur auf die nächstliegende Fahrbahn führen. *Google Maps oder andere Karten die Straßen so anzeigen. === Wie man zwei Einbahnen zu einer Fahrspur vereint === Wer eine Straße in zwei Fahrspuren aufteilt, sollte auch verstehen, was alles dazugehört, dies rückgängig zu machen. Es gibt leider keinen einfachen Weg zwei getrennte Fahrspuren wieder in eine zweispurige Straße zurückzuwandeln. Deshalb sollte man sich das Aufteilen gut überlegen. Wenn man eine Straße antrifft, die nicht aufgeteilt sein sollte, erkennt man dies sehr gut an der Summe der Fehlermeldungen der User. Dort wo die meisten Meldungen liegen brennt es in der Regel. Danach beginnt die hohe Kunst der Karten-Chirurgie am Waze-Karteneditor. Folgende Schritte sind zu erledigen: #Löschen der einen oder anderen Seite inkl. der Segmente, die beide Straßen verbinden. #Alle verwaisten Kreuzungen entfernen. #Richtungsänderungen an der verbleibenden Straße vornehmen. #Alle Abbiegeverbote kontrollieren. #Verbinden inkl. Abbiegeverbote aller Straßen, die in die verbleibende Straße münden. #Sicherstellen, dass die verleibende Straße korrekt in beide Richtungen verbunden ist. #Die Geometrie der zweispurigen Straße in die Mitte korrigieren. <br/>Damit man sich damit nicht zu viel Arbeit einheimst, sollte man vorher die richtige Straße auswählen, die verbleiben soll. Dies entscheidet man natürlich anhand der bereits verbundenen Segmente. Man kann auch übers Kreuz löschen damit man schneller vorwärts kommt. Nicht vergessen die verbleibende Straße wieder korrekt mit ihr selbst zu verbinden. === Autobahnen und Anschlüsse === Langstrecken-Navigation ist nicht möglich, wenn die Autobahnen nicht korrekt verbunden sind. Deshalb ist diesem Thema besondere Aufmerksamkeit zu widmen. Man kann sehr viel bewirken, wenn man diese korrekt erstellt. Besondere Überlegungen müssen bei eingeschränkt befahrbaren Straßen angestellt werden. Es kann bei unsorgfältiger Vorgehensweise auch mehr Schaden enstehen, als an normalen Quartierstraßen. ==== Straßen ==== Beschränkt zugängliche Straßen mit mehreren Spuren in beiden Richtungen, die durch ein Hindernis zwischen den Spuren abgetrennt sind und allein durch Rampen zugänglich sind, sollten fast immer in zwei Einbahnen aufgeteilt werden. Andere normale Straßen sollten meistens nicht aufgeteilt werden. ==== Ein- und Ausfahrten ==== Einfahrten sollten nach der Richtung in die sie führen benannt werden. Ausfahrten sollten nach der Ausfahrtnummer - wenn vorhanden - und auch der Beschilderung der Ausfahrten benannt werden. Ein- und Ausfahrten sollten immer auf “Gesperrt“ gesetzt werden, um die Richtung zu erhalten, da viele auch eine naheliegende entgegengesetzte Spur besitzen. Werden solche Segmente nicht gesperrt, wird man früher oder später das Ganze nochmal bearbeiten müssen, wenn sich die Richtung einer Ein- oder Ausfahrt geändert hat. Dabei auch gleich die Verbindungen und Abbiegeverbote kontrollieren, bevor Segmente gesperrt werden. *Es gibt in den länderspezifischen Wikis mehr Informationen zur Benennung. *Verstehe den Unterschied zwischen Ein- und Ausfahrten und ebenerdigen [[Abbiegespuren]] ==== Über- und Unterführungen ==== Erfahrungen haben gezeigt, dass es sinvoller ist einzelnen bestimmten Segmenten einen unterschiedlichen Level zu geben, als längeren Straßen die nicht durch Kreuzungen unterteilt sind. Autobahnen beispielsweise sollten generell auf Level 0 bleiben. Brücken die darüber führen Level 1. Über- oder Unterführungen sollten nicht Level 0 haben. Auch bei komplizierten Verzweigungen sollten die Levels den tatsächlichen Zustand widerspiegeln. Trifft man auf Segmente, die bereits im Level verändert wurden, muss man dem Drumherum besondere Aufmerksamkeit schenken, damit nicht fehlerhafte Levels entstehen an Straßen, die bereits korrekt erstellt wurden. In den meisten einfachen Fällen können Probleme beseitigt werden, wenn man den Level eines Segments ändert. Bei komplizierten Kreuzungen kann es hilfreich sein, eine Zeichung zu erstellen oder man schaut sich zuerst die höchst- oder tiefstliegendsten Segmente an, um sich Klarheit zu verschaffen. Gelegentlich kommt man auch an eine Kreuzung, wo die Levels auf den ersten Blick keinen Sinn ergeben. Es kann daher hilfreich sein, ein Segment durch eine Kreuzung zu unterteilen. Es bleibt dann zu hoffen, dass nicht jemand die Kreuzung löscht ohne sich vorher zu vergewissern, wieso die da ist. ==== Ebenen in Straßen ==== Egal welche Ebene eine Straße besitzt, wenn sie durch eine Kreuzung verbunden wird, wird die ganze Verzweigung navigierbar. Wenn man eine Über- oder Unterführung findet, die mit der darüber- oder darunterliegenden Straße durch eine Kreuzung verbunden ist, so ist diese Kreuzung zu löschen. Waze navigiert die Benutzer sonst von einer Brücke auf eine draunterliegende Straße (oder umgekehrt), was nicht sehr sinnvoll ist. Man vergewissert sich dabei zuerst, ob die Ebenen der kreuzenden Straßen und die Benennung der einzelnen Segmente gleich sind. Ansonsten kann die Kreuzung nicht gelöscht werden. Desweiteren kann man dies auch mit der Brücken-Funktion beheben. ==== Brücken-Funktion ==== Zwei Segmente, die über- oder unterführen auswählen und das Brückensymbol anklicken. Die beiden Segmente vereinen sich und der Level erhöht sich automatisch auf Level 1. Falls damit kein Erfolg erzielt wird muss man allf. die Segmente einzeln abtrennen und neu verbinden. Verbindest Du mit der Brücken-Funktion Segmente, die unterschiedliche Levels besitzen, erhöht sich der Level um einen höher, als das Segment mit dem höchsten Level. ==== Für Normalverkehr gesperrt oder zeitlich beschränkte Fahrverbote ==== Inzwischen unterstützt Waze auch [[Straßensperrungen und zeitlich beschränkte Fahrverbote|zeitlich beschränkte Fahrverbote]], Richtungswechsel zu bestimmten Zeiten oder Straßen, die für bestimmte Fahrzeuge reserviert sind. Diese Straßen haben manchmal eigene Einfahrten und führen parallel entlang normaler Straßen. Das Routing kann dadurch Anweisungen geben, die falsch sind oder gar tödlich enden können! Die einfachste Lösung war bisher, diese Straßen zu löschen, falls sie bereits erstellt wurden. Dies ist jedoch nicht erwünscht. Daher ist es sinnvoll, die erweiterten Eigenschaften möglichst überall hinzuzufügen. === Wann sind Ramps an Kreuzungen zu verwenden === Siehe hier [[Abbiegespuren]] === Wann ein Kreisverkehr erstellt werden soll === Wenn klar ist, wie man [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehre]] erstellt, ist es die richtige Zeit alle Kreisel, die nur aus einzelnen Straßen Segmenten gezeichnet wurden auszutauschen und durch richtige Kreisverlehre zu ersetzen. Das gleiche gilt für Kreisverkehre der Basis-Karte (Base Map), die ganz leicht an ihrer seltsam eckigen Form erkannt werden können. Spätestens nach dem Korrigieren wird einem klarwerden, wie die [[Erstellen und bearbeiten eines Kreisverkehrs|korrekten Ansagen]] bei der Navigation zustandekommen. === Richtung und Sperren von Straßen === '''Wozu sperrt man Segmente?''' Die "Sperren"-Funktion bewirkt gem. [[Häufig gestellte Fragen#Was ist eine gesperrte Straße im Waze Map-Editor.3F|den Häufig gestellten Fragen]] folgendes: *Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]]. *Zwingt das Routing, den verbundenen Segmenten zu folgen und macht es nahezu unmöglich, gegen die definierte Fahrtrichtung zu Routen. '''Wann sperrt man Segmente?''' ''[[Wichtig: Unvollständige Segmente werden nicht gesperrt.]]'' Grundsätzlich bleiben Straßen frei. Waze lebt von den Beiträgen vieler, und jeder soll die Möglichkeit behalten, aktuelle Änderungen an Straßen schnell und einfach einzutragen. Sperren sollten also nur auf wichtigen Straßen vorgenommen werden, wo durch die Bearbeitung durch Einsteiger gravierende Auswirkungen, insbesondere auf den überregionalen Verkehr zu befürchten sind. Folgende Straßen müssen gelockt werden, wenn sie vollständig bearbeitet sind: *Autobahnen samt den zugehörigen Auf- und Abfahrten: Level 4 oder 5 *Bundesstraßen: Level 3 Wenn diese Straßen durch einen Editor niedrigen Ranges erstellt oder bearbeitet wurden, fordert er die Sperrung mit dem richtigen Level im Forum an. '''Informiere Dich in den länderspezifischen Wikis über die Gegebenheiten im betreffenden Land!''' === Konnektivität === Nur weil sich zwei Segmente an einer Kreuzung berühren, heißt dies noch nicht, dass sie auch korrekt miteinander verbunden sind. Abbiegeverbote kontrollieren! === Unnötige Kreuzungen === Unnötige Kreuzungen sind zu entfernen, da sie oft zu fehlerhaften Verbindungen und falschen Straßennamen führen. Zudem sind sie für das [[Wie Waze Routen kalkuliert|Routing]] nicht von Vorteil, da pro Kreuzung ein Zuschlag von 5 Sekunden zur Fahrzeitberechnung addiert wird. Ausnahmen bilden Orts- oder Landesgrenzen, oder wenn man in Kürze eine Straße mit einer Kreuzung verbindet. Wenn Kreuzungen entfernt werden, muss darauf geachtet werden, dass die Segmente die gleichen Eigenschaften besitzen. Andernfalls kann die Kreuzung nicht entfernt werden. Kreuzungen auf Straßen mit der Eigenschaft "Unbekannt" können aus Sicherheitsgründen nicht gelöscht werden. Straßen in Richtung ändern und nach dem Entfernen der Kreuzung allf. wieder auf "Unbekannt" setzen. == Neue Straßen == === Aufzeichnen mit der Waze-App === Nach dem Aufzeichnen muss die Straße im Editor bearbeitet werden. Aufgezeichnete und unbearbeitete Straßen tauchen zwar in der App auf, sie werden aber nicht für das Routing benutzt. '''Man sollte diesen Anweisungen folgen:''' #Geometrie ausrichten anhand der Luftaufnahme, sofern diese am richtigen Ort ist in der Gegend. Dies sollte mit der Ebene GPS-Punkte geprüft werden. Kanten und Ecken abrunden wo nötig. #Korrekter Straßentyp und Name anhand der Definition des Landes einfügen. #Die korrekte Fahrtrichtung bestimmen. #Kreuzungen hinzufügen und Straßen korrekt verbinden. <br/>Wenn mit dem Bearbeiten einer neuen Straße (rot) begonnen wird, wird die Straße ohne Typenänderung weiß erscheinen. Nach dem nächsten Kartenupdate von Waze, wird diese dann auf der Echtzeit-Karte und der Waze-App zu sehen sein. Daher ist es nicht sehr hilfreich, eine unfertige Straße zu hinterlassen. Solange sie rot ist, merkt mann noch, dass die Straße bearbeitet werden muss. Aber sobald sie weiß wird, kann sie im Karteneditor nicht mehr so schnell identifiziert werden. Wenn sie nur weiß ist und auch einen Straßennamen hat, mag dies gut aussehen, aber Waze weiß vielleicht noch nicht, dass die Straße befahren werden kann. == Parkings und Parkplätze == Das Zuordnen eines Parkplatzes und dessen Straßen dient zwei Zwecken: *es erlaubt Waze eine Tür-zu-Tür-Navigation innerhalb des Parkplatzes *es erlaubt Waze von einer Hauptstraße weg zu navigieren, um fehlerhafte Verkehrsmeldungen zu vermeiden ==== Gebrauch des "Parkplatz"-Straßentyps ==== "Parkplatz" ermöglicht das Erstellen von Parkplätzen und verhindert gleichzeitig, dass der Routing-Server diese für die Navigation miteinbezieht. Damit nicht durch Parkplätze geroutet wird, hat Waze den Routing-Algorithmus im Juni 2012 geändert. Jedes Segment, das sich innerhalb eines Parkplatzes befindet ist daher als "Parkplatz" zu definieren. ==== Einkaufszentren ==== Wenn ein Parkplatz eines Einkaufszentrums erstellt wird, sollten Haupteinfahrten und die wichtigsten Verbindungen erstellt werden, Verbindungen zwischen verschiedenen Parzellen eines Parkplatzes und entlang der Geschäfte. Die meistgebrauchten Spuren sollten dabei miteinbezogen werden. Am wichtigsten sind hier Benutzerfreundlichkeit und Einfachheit. Es macht keinen Sinn, jedes einzelne Parkfeld mit einem Segment zu bestücken, dies lässt die Karte auf der App nur unübersichtlich aussehen. ==== Kleinere Parkplätze ==== Parkplätze, die einer kleinen Anzahl von Unternehmen dienen, sollten minimal sein. Genug, um dem Fahrer richtige Richtungen, Ein- und Ausfahrten zu zeigen und den Weg zu einem Geschäft. Manchmal reicht ein einziges paralleles Segment. ==== Durchfahrts-Parkplätze ==== Diese sollten nicht zu viele Einbahnen enthalten und am besten mit einer Einbahn als Schlaufe durch den Parkplatz führen. Man bedenke dabei, dass sich eine [[WME Schnellstart-Anleitung#Straßen-Schlaufen|Straße]] nicht mit sich selbst verbindet. ==== Parkhäuser ==== Wenn ein Parkhaus nur eine Ein- und Ausfahrt besitzt, sollte diese mindestens auf der Karte erscheinen. Ein einzelnes zweispuriges Segment reicht aus, da im Parkhaus meistens kein GPS-Signal vorhanden ist. Der Straßentyp ist "Parkplatz" und das Parkhaus kann mit einem Orientierungspunkt versehen werden. Besitzt das Parkhaus separate Ein- und Ausfahrten, so sollte eine Durchfahrt ermöglicht werden. Dazu reicht in den meisten Fällen ein einziges Segment. Es ist nicht nötig, jedes Stockwerk des Parkhauses darzustellen, dies macht die Karte nur unnötig unübersichtlich. == Unterdrücken von Verkehrsmeldungen und Kartenfehlern == Straßentyp "Parkplatz", Orientierungspunkte "Parkplatz" und "Tankstelle" verhindern serverseitig die Entstehung von Kartenfehlern.<br/>Orientierungspunkte "Parkplatz" und "Tankstelle" verhindern eine Staumeldung, daher dürfen sie nicht an angrenzende Haupt- oder Straßen herangezeichnet werden, sondern dürfen nur den Parkplatz oder die Tankstelle selbst einschließen. == Klassifizierung von Kreuzungen == Verschiedene Arten von Kreuzungen haben [[Classification of crossings|Standard-Möglichkeiten]], um diese zu bearbeiten. Interessant sind auch diese Seiten:<br/>[[Kreuzungen]]<br/>[[Abbiegespuren]] <center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br/>[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 446c86e5b070c7c1889bf1df5c517ab934df1356 0 23 65 64 2014-04-16T15:06:54Z Kentsmith9 25 Fixed double redirect wikitext text/x-wiki #REDIRECT [[Waze symbols]] 694ccc99341800635fc49c19be05bfab9495293e 0 78 432 431 2014-04-23T20:50:10Z Kentsmith9 25 /* Exceptions */ Added construction wikitext text/x-wiki When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road types/USA#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation. == Should the connector be mapped? == First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes. There are only a few situations in which connectors are called for in an intersection: *When the turn lane physically separates from the main road well in advance of the intersection *When the turn lane is far enough from the point of intersection on the map (due to the size of the intersection or the angle at which the roads meet) that the driver might overshoot while waiting for a delayed "turn" audible, or that the Waze client might become confused and disrupt navigation *When the area is "busy" enough that the driver may not get any advance warning that a turn is coming up--in which case a connector lets you notify the driver a little earlier *When there are user complaints ([[Update_Requests_in_Waze_Map_Editor|Update Requests]]) that the audible was too late, or that the map should have shown a connector When in doubt, leave it out. Each connector complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc. == {{anchor|How to label the connector type}} Road type == Although sometimes referred to as ramps, to Waze these are '''not''' ramps. Ramps in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below. The connector segment's type should be set based on the '''lowest''' of the types of roads it connects. *Ex: Street to Minor Highway should be Street type. *Ex: Minor Highway to Primary Street should be Primary Street type. *Ex: Primary Street to Primary Street should be Primary Street type. Example: [[Image:At-grade_example1.jpg]] Also note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection. == {{anchor|How to name the connector}} Road name == In most cases, leaving the segment unnamed will be sufficient. Navigation instructions will simply use the name of the segment to which the connector segment connects. If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector. == {{anchor|Geometry of the connector}} Geometry == The [[Junction Style Guide]] provides significant information on how to best set the geometry of the connector to get the best routing and text-to-speech result. Be sure to review that article when updating or creating these connectors. == {{anchor|Turn restrictions necessary for proper connector routing}} Turn restrictions == Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler. In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector. [[Image:Atgrade example3.jpg]] AND, at the end of the connector, the left turn must be restricted: [[Image:Atgrade example2.jpg]] If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function: [[Image:Atgrade example4.jpg]] == Exceptions == {{construction | contact = http://www.waze.com/forum/viewtopic.php?f=276&t=86666 | contacttype = forum | draft = yes | open = no | revision = yes | section = yes | talk = no }} === Connector is a signed, numbered exit === [[File:GSP_10.jpg|right|border]] '''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA. The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes reduce and exits become a mix of grade separated ramps and at-grade intersections. In order to receive an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction for Exit Right]] rather than Keep Right or Turn Right, this connector needs to be a ramp. {{clear}} {|style="margin: 0 auto;" |- valign="top" | [[File:GSP_10A.jpg|x162px]] | [[File:GSP_10B.jpg|x162px]] | Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south). |} [[Category:Style Guides]] [[Category:Waze Map Editor]] [[Category:Update what links here]] e7e89e92faa115bff598e2cc4c50c67c2c17e9dd 0 96 663 662 2014-04-25T01:56:21Z Kentsmith9 25 /* Parking Lots */ fixed link wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_rank#Unlocking_segments_above_your_rank|unlocking segments above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 8b6b8420f244673b113406747734099524644eaa 664 663 2014-05-30T20:58:17Z Kentsmith9 25 Improved link wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help Area Managers and others design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for regular editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_restrictions#Unlocking_an_object_above_your_rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] f1f0754a9ebcdc9df0d2e00d85145bb57e7f0713 665 664 2014-05-31T02:35:23Z Kentsmith9 25 Clarified the information is for all editors wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_restrictions#Unlocking_an_object_above_your_rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 861da3de2d476ce27dbfafa99dc4ce1444209124 666 665 2014-06-07T12:14:05Z Kentsmith9 25 Added template wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{:Local_vs_global_guidance/Mbox}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_restrictions#Unlocking_an_object_above_your_rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] b7377b4a2614949714a6066cfe82aaafad277a8c 667 666 2014-06-09T15:51:57Z Kentsmith9 25 Moved to template box wikitext text/x-wiki [[Waze Map Editor|Back to Editing Manual]] The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_restrictions#Unlocking_an_object_above_your_rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. [[Waze Map Editor|Back to Editing Manual]] [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 9b1fffeb2f5b56557d7ee574e598c2607622421b 0 8 18 2014-05-01T20:44:51Z Kentsmith9 25 Created dab wikitext text/x-wiki '''Area''' may refer to: * [[Area Manager]], an editor with access to edit beyond their driven limits * [[Editable area]], the actual map area in which that you can edit * [[Places#Area|Area place]], a point-of-interest location with a defined region {{Disambig}} b50c2858e1a4939e6be67a222df103977b7ad269 19 18 2014-05-02T00:45:52Z Kentsmith9 25 Kentsmith9 moved page [[Area]] to [[Area (disambiguation)]]: more appropriate name wikitext text/x-wiki '''Area''' may refer to: * [[Area Manager]], an editor with access to edit beyond their driven limits * [[Editable area]], the actual map area in which that you can edit * [[Places#Area|Area place]], a point-of-interest location with a defined region {{Disambig}} b50c2858e1a4939e6be67a222df103977b7ad269 0 9 22 2014-05-02T00:45:52Z Kentsmith9 25 Kentsmith9 moved page [[Area]] to [[Area (disambiguation)]]: more appropriate name wikitext text/x-wiki #REDIRECT [[Area (disambiguation)]] c190adc666a79c2a65784d362bd49d950f125b14 10 58 11744 11743 2014-05-15T19:59:13Z Kentsmith9 25 Added Mail type wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox warning yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | mail = Mbox mail.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> {{Documentation|content=This subtemplate supports the default values of {{tl|Mbox}}. It should not be altered without review from a Wiki Expert. Contact one through the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion forum.]}} <!-- This category is only for the template itself --> [[Category:Template:Mbox]] </noinclude> 5c02a7f3ed88b482f214e62e4bbe59341b1492f3 11745 11744 2014-06-27T00:33:30Z Kentsmith9 25 Added forum icon wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox warning yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | mail = Mbox mail.png | forum = Gnome-system-users.svg.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> {{Documentation|content=This subtemplate supports the default values of {{tl|Mbox}}. It should not be altered without review from a Wiki Expert. Contact one through the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion forum.]}} <!-- This category is only for the template itself --> [[Category:Template:Mbox]] </noinclude> 8002e6f1d053ccc892d1d18732e9dcf0242bc2d8 0 11 26 2014-05-28T15:36:52Z Kentsmith9 25 created redirect wikitext text/x-wiki #REDIRECT [[Chat (disambiguation)]] 743a89ebae709c05f34bf41ea243fe1cb7c41084 0 10 23 2014-05-28T15:41:26Z Kentsmith9 25 Created disambiguation page wikitext text/x-wiki '''Chat''' may refer to: * [[Waze Map Editor/Chat|Waze Map Editor Chat]], a built-in chat function linking map editors * [[How_to_Report#Map_chat|Map chat]], a client app chat function linking drivers {{Disambig}} 118447cf12d74eb1f830b07257bc9800073d3d42 10 67 205 2014-06-09T17:11:09Z Kentsmith9 25 Create redirect wikitext text/x-wiki #REDIRECT [[Template:About Waze]] 7def93ded21322c704e65158c36ca011ec2dcc7a 10 37 11465 11464 2014-06-18T00:52:56Z Kentsmith9 25 1 revision wikitext text/x-wiki <includeonly>-moz-border-radius: {{{1|8px}}}; -webkit-border-radius: {{{1|8px}}}; border-radius: {{{1|8px}}};</includeonly><noinclude> <!-- ADD CATEGORIES AND INTERWIKIS TO THE /doc PAGE, NOT HERE, THANKS --> {{documentation}} </noinclude> af4350db0626148ae24dd33131e6291b623f4945 10 44 11521 11520 2014-06-18T00:52:56Z Kentsmith9 25 1 revision wikitext text/x-wiki {{key press/core|{{{1|}}}}}<!-- -->{{#if:{{{2|}}}|{{{chain first|{{{chain|+}}}}}}{{key press/core|{{{2}}}}}}}<!-- -->{{#if:{{{3|}}}|{{{chain second|{{{chain|+}}}}}}{{key press/core|{{{3}}}}}}}<!-- -->{{#if:{{{4|}}}|{{{chain third|{{{chain|+}}}}}}{{key press/core|{{{4}}}}}}}<!-- -->{{#if:{{{5|}}}|{{{chain fourth|{{{chain|+}}}}}}{{key press/core|{{{5}}}}}}}<!-- -->{{#if:{{{6|}}}|{{{chain fifth|{{{chain|+}}}}}}{{key press/core|{{{6}}}}}}}<!-- -->{{#if:{{{7|}}}|{{{chain sixth|{{{chain|+}}}}}}{{key press/core|{{{7}}}}}}}<!-- -->{{#if:{{{8|}}}|{{{chain seventh|{{{chain|+}}}}}}{{key press/core|{{{8}}}}}}}<!-- -->{{#if:{{{9|}}}|{{{chain eighth|{{{chain|+}}}}}}{{key press/core|{{{9}}}}}}}<!-- -->{{#if:{{{10|}}}|{{{chain ninth|{{{chain|+}}}}}}{{key press/core|{{{10}}}}}}}<!-- -->{{#if:{{{11|}}}|[[Category:Wikipedia keypress template parameter needs fixing]]}}<noinclude> {{documentation}} <!-- add category and language links to the /doc sub-page, not here --> </noinclude> ec13a6d48bf0d5a168557926c766b9bc533d0506 10 38 11468 11467 2014-06-18T00:52:57Z Kentsmith9 25 1 revision wikitext text/x-wiki <includeonly>-moz-box-shadow: {{{1|4px}}} {{{2|4px}}} {{{3|4px}}} {{{4|#CCC}}}; -webkit-box-shadow: {{{1|4px}}} {{{2|4px}}} {{{3|4px}}} {{{4|#CCC}}}; box-shadow: {{{1|4px}}} {{{2|4px}}} {{{3|4px}}} {{{4|#CCC}}};</includeonly><noinclude> <!-- ADD CATEGORIES AND INTERWIKIS TO THE /doc PAGE, NOT HERE, THANKS --> {{documentation}} </noinclude> 1f26926e3b1ad5bb5e0ed09f9a1ac2a9a1d47997 10 39 11476 11475 2014-06-18T00:52:57Z Kentsmith9 25 1 revision wikitext text/x-wiki <div style="clear:{{{1|both}}};"></div><noinclude>{{doc}}</noinclude> 15e943687be5d8f8e27fa6cc7813bbfa85df72a9 10 45 11524 11523 2014-06-18T00:52:58Z Kentsmith9 25 1 revision wikitext text/x-wiki <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; {{border-radius|0.2em}} {{box-shadow|0.1em|0.2em|0.2em|#ddd}} background-color: #f9f9f9; {{linear-gradient|top|#eee, #f9f9f9, #eee}} padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">{{#switch:{{lc:{{{1}}}}} | caps lock = {{Unicode|⇪}} Caps Lock | [[caps lock]] = {{Unicode|⇪}} [[Caps Lock]] | shift = {{Unicode|⇧}} Shift | [[shift key|shift]] = {{Unicode|⇧}} [[Shift key|Shift]] | enter = {{Unicode|↵}} Enter | [[enter key|enter]] = {{Unicode|↵}} [[Enter key|Enter]] | cmd = {{Unicode|⌘}} Cmd | [[cmd key|cmd]] | [[command key|cmd]] = {{Unicode|⌘}} [[Command key|Cmd]] | command = {{Unicode|⌘}} Command | [[cmd key|command]] | [[command key|command]] = {{Unicode|⌘}} [[Command key|Command]] | opt = {{Unicode|⌥}} Opt | [[opt key|opt]] | [[option key|opt]] = {{Unicode|⌥}} [[Option key|Opt]] | option = {{Unicode|⌥}} Option | [[option key]] | [[opt key|option]] | [[option key|option]] = {{Unicode|⌥}} [[Option key|Option]] | tab = Tab {{Unicode|↹}} | [[tab key|tab]] = [[Tab key|Tab]] {{Unicode|↹}} | backspace = ← Backspace | [[backspace]] = ← [[Backspace]] | win = {{Unicode|⊞}} Win | [[win key|win]] | [[windows key|win]] = {{Unicode|⊞}} [[Windows key|Win]] | menu = {{Unicode|≣}} Menu | [[menu key|menu]] = {{Unicode|≣}} [[Menu key|Menu]] | up = ↑ | [[arrow keys|up]] = [[Arrow keys|↑]] | down = ↓ | [[arrow keys|down]] = [[Arrow keys|↓]] | left = ← | [[arrow keys|left]] = [[Arrow keys|←]] | right = → | [[arrow keys|right]] = [[Arrow keys|→]] | * | asterisk = <nowiki>*</nowiki> | # | hash = <nowiki>#</nowiki> | [[#]] = [[Number sign|#]] | : | colon = <nowiki>:</nowiki> | [[:]] = [[Colon (punctuation)|:]] | pipe = <nowiki>|</nowiki> | [[|]] = [[Pipe symbol|<nowiki>|</nowiki>]] | ; | semicolon = <nowiki>;</nowiki> | [[;]] = [[Semi-colon|<nowiki>;</nowiki>]] | equals = <nowiki>=</nowiki> <!-- Left & right analog sticks --> | l-up | l up = L↑ | l-down | l down = L↓ | l-left | l left = L← | l-right | l right = L→ | l-ne | l ne = L↗ | l-se | l se = L↘ | l-nw | l nw = L↖ | l-sw | l sw = L↙ | r-up | r up = R↑ | r-down | r down = R↓ | r-left | r left = R← | r-right | r right = R→ | r-ne | r ne = R↗ | r-se | r se = R↘ | r-nw | r nw = R↖ | r-sw | r sw = R↙ <!-- PlayStation --> | ps x | ex = {{unicode|×}} | ps c | circle = {{unicode|○}} | ps s | square = {{unicode|□}} | ps t | triangle = {{unicode|△}} <!-- Nintendo 64 & GameCube --> | c-up | c up = C↑ | c-down | c down = C↓ | c-left | c left = C← | c-right | c right = C→ | c-ne | c ne = C↗ | c-se | c se = C↘ | c-nw | c nw = C↖ | c-sw | c sw = C↙ <!-- default --> | #default = {{{1}}} }}</kbd><noinclude> {{documentation}} <!-- Add categories and interwikis links to the /doc subpage, not here! --> </noinclude> 03657747b458c57b74fdc4e0925eb5776ac2eccf 10 46 11527 11526 2014-06-18T00:53:01Z Kentsmith9 25 1 revision wikitext text/x-wiki <includeonly>background-image: -moz-linear-gradient({{{1|}}}, {{{2|}}}); background-image: -o-linear-gradient({{{1|}}}, {{{2|}}}); background-image: -webkit-linear-gradient({{{1|}}}, {{{2|}}}); background-image: linear-gradient({{Linear-gradient/legacy|{{{1|}}}}}, {{{2|}}});</includeonly><noinclude> <!-- ADD CATEGORIES AND INTERWIKIS TO THE /doc PAGE, NOT HERE, THANKS --> {{documentation}} </noinclude> c8f4766d7ac860c26118a121480308ed58699a4a 10 47 11530 11529 2014-06-18T00:53:02Z Kentsmith9 25 1 revision wikitext text/x-wiki {{#switch: {{{1|}}} | top = to bottom | bottom = to top | left = to right | right = to left | top left | left top = to bottom right | top right | right top = to bottom left | bottom left | left bottom = to top right | bottom right | right bottom = to top left | #default = {{{1}}} }} 519d0c5417b418a0e87b1360cd516f177ddc6ea4 10 68 11881 11880 2014-06-18T00:53:04Z Kentsmith9 25 1 revision wikitext text/x-wiki <includeonly><code><nowiki>{{</nowiki>{{#if:{{{subst|}}}|[[Help:Substitution|subst]]:}}[[{{{LANG|}}}{{{SISTER|}}}{{ns:Template}}:{{{1|}}}|{{{1|}}}]]<!-- -->{{#if:{{{2|}}}| &#124;{{{2}}} }}<!-- -->{{#if:{{{3|}}}| &#124;{{{3}}} }}<!-- -->{{#if:{{{4|}}}| &#124;{{{4}}} }}<!-- -->{{#if:{{{5|}}}| &#124;{{{5}}} }}<!-- -->{{#if:{{{6|}}}| &#124;{{{6}}} }}<!-- -->{{#if:{{{7|}}}| &#124;{{{7}}} }}<!-- -->{{#if:{{{8|}}}| &#124;{{{8}}} }}<!-- -->{{#if:{{{9|}}}| &#124;{{{9}}} }}<!-- -->{{#if:{{{10|}}}| &#124;{{{10}}} }}<!-- -->{{#if:{{{11|}}}| &#124;{{{11}}} }}<!-- -->{{#if:{{{12|}}}| &#124;''...'' }}<nowiki>}}</nowiki></code></includeonly><noinclude> {{documentation}} <!-- Add categories and interwikis to the /doc subpage, not here! --> </noinclude> 9e77b8a4aac1a981527cef2e034bdf46f87d9a64 10 55 11708 11707 2014-06-18T00:53:05Z Kentsmith9 25 1 revision wikitext text/x-wiki <span class="Unicode">{{{1}}}</span><noinclude> {{documentation}} </noinclude> ff038df4400b7f63b01ab8dbd458bcb16437c79c 10 60 11753 2014-06-29T07:05:25Z Kentsmith9 25 Created template wikitext text/x-wiki {{#if:{{{2|}}} |<span style="font-size:{{{1|}}};">{{{2|}}}</span> |<span style="font-size:90%;">{{{1}}}</span> }}<noinclude> {{documentation}} {{Template:Resize/TemplateData}} <!--PLEASE ADD CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS--> </noinclude> a8de5b0bab808ae5f4574969c09a4e87722f403a 10 75 373 372 2014-07-03T11:09:26Z Alexnrocha 61 wikitext text/x-wiki <span style="color: red;">''The specific details of the Area Manager role are currently under review within the Waze community. Some of the information below is currently out of date. Please review the [http://www.waze.com/forum forums] for more information. Once the role changes are finalized, this section will be updated as required.''</span> <br/>An Area Manager, AM for short, is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Respond to and correct user update requests on the [[Update Requests in Waze Map Editor|Update Requests]] layer. *Process and resolve map errors/problems as shown on the [[Map Problems in Waze Map Editor|Map Problems]] layer. *Make changes to the map when road construction projects start and finish by maintaining new geometry, adding or deleting roads and disconnecting and re-connecting ramps. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Act as a mentor to other editors, offering advice in both the forums and when you see improper edits on the map. == How to Become an Area Manager == The position of Area Manager is by appointment. To become an area manager, you must meet the prerequisites and then submit your application. Prospective Area Managers should already... *have at least a few months of experience editing the Waze maps regularly. *have read and followed the guidelines for mapping found in the wiki, starting at the Waze Map Editing page. *have completed at least 5000 quality edits. *have a real Waze username which does not start with usa_ or world_. *have their state and/or country in their forum profile. *have forum PMs enabled and associated with a valid and verifiable email address. *be active in the Waze forums, asking questions, and even providing guidance for newer editors, if possible. *know who their regional coordinator is. (Knowing the correct answer to this is a strong indicator as to how much reading an applicant has done of the forums and Wiki). === Required Reading === Before applying to become an AM, you will be expected to have read the following wiki pages and forums. '''Wiki''' *[[Map Editing Quick-start Guide]] *[[Best map editing practice]] *[[Map Editing Tips and Hints]] *[[Waze Map Editor|Waze Map Editor]] and all the [[Waze Map Editor#Editing Manual|Editing Manual]] links therein ''Be sure to also find and read the editing guidelines specific to your country.'' '''Forum''' You should also read these two forums and know where the Unlock Request is located *[http://www.waze.com/forum/viewtopic.php?f=636&t=45237%7C READ ME FIRST! General forum guidelines] *[http://www.waze.com/forum/viewtopic.php?t=32072%7C Unlock Request Instructions] *[http://www.waze.com/forum/viewforum.php?f=265%7C Unlock Request] == Area Manager application process == ==== Identifying your area ==== Before you head off to submit your application for AM, use the [[Map Editing (new Editor)|Waze Map Editor]], position the map and set the zoom level to show the area you want to manage. Make a [[Map Editing (new Editor)#Permalink|Permalink]] of the area and copy the address from the address bar in your browser. === Area Manager territory === *More than one Area Manager can manage the same area. *Areas can overlap, be smaller or larger. *You can also be the AM for more than one area. Notice the green area of the map has four managers. [[File:AreaManagerLayer.png]] === The application === If you would like to become an Area Manager, or expand your existing area, you will need to '''complete the appropriate application form for your country'''. The following countries have a self management system and requests will be approved by country managers or coordinators. ''Please go to the relevant [http://www.waze.com/forum/viewforum.php?f=19 country forum] to find the appropriate application form:'' *[http://www.waze.com/forum/viewforum.php?f=645 USA] *[http://www.waze.co.il/forum/viewforum.php?f=38 Israel] *[http://www.waze.com/forum/viewforum.php?f=55 United Kingdom] *[http://www.waze.com/forum/viewforum.php?f=25 Hungary] *[http://world.waze.com/forum/viewforum.php?f=26 Spain] *[http://www.waze.com/forum/viewforum.php?f=279 Malaysia] / [http://www.waze.com/forum/viewforum.php?f=191 Singapore] / Brunei *[https://www.waze.com/forum/viewtopic.php?f=331&t=29288 Brazil] *[http://www.waze.com/forum/viewforum.php?f=20 Italy] *[http://www.waze.com/forum/viewforum.php?f=700 Belgium] / [http://www.waze.com/forum/viewforum.php?f=21 The Netherlands] / [http://www.waze.com/forum/viewforum.php?f=381 Luxembourg] *[http://www.waze.com/forum/viewforum.php?f=24 Germany / Austria / Switzerland] *[http://www.waze.com/forum/viewforum.php?f=34 France] *[http://www.waze.com/forum/viewforum.php?f=440 Chile] *[http://www.waze.com/forum/viewforum.php?f=611 Portugal] *[http://www.waze.com/forum/viewforum.php?f=22 Czech republic & Slovakia] *[http://www.waze.com/forum/viewforum.php?f=465 Mexico] *[http://www.waze.com/forum/viewforum.php?f=33 Sweden] *[https://www.waze.com/forum/viewtopic.php?f=359&t=88599 Paraguay] *[http://www.waze.com/forum/viewforum.php?f=309 Philippines] *[http://www.waze.com/forum/viewforum.php?f=171 India] *[http://www.waze.com/forum/viewforum.php?f=120 Romania] *[http://world.waze.com/forum/viewtopic.php?f=56&t=59583 Australia] *[https://www.waze.com/forum/viewtopic.php?f=501&t=64255 Costa Rica] '''For all other countries''', AM requests should be [https://docs.google.com/a/waze.com/spreadsheet/viewform?formkey=dGl6TVF2bzFtdHRWUDVzR3N5TllZanc6MA#gid=0 submitted via this form] and will be handled directly by Waze support. == Area Manager Links == *[[Waze Map Editor|Map Editing]] *[[Best map editing practice]] *[[Area Manager: Diagnosis]] *[[Area Manager: Tips and Tricks]] <!-- * [[Area Manager: YouTube Training Videos]]--> *[[Area Manager: How to edit wiki pages]] *[[Known issues]] *Road Types: [[Road Types (USA)|(USA)]], [[Road Types India|India]] *[[Junction Style Guide|Junction Style Guide]] *[[Area Manager: 101]] == List of Area Managers == See [http://bit.ly/WazeAMs List of Area Managers and their preferred contact details]. 74c56c1130afb45af03a0443f70cfeb2cc9eb534 374 373 2014-07-03T16:18:03Z Kentsmith9 25 fixed https wikitext text/x-wiki <span style="color: red;">''The specific details of the Area Manager role are currently under review within the Waze community. Some of the information below is currently out of date. Please review the [http://www.waze.com/forum forums] for more information. Once the role changes are finalized, this section will be updated as required.''</span> <br/>An Area Manager, AM for short, is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Respond to and correct user update requests on the [[Update Requests in Waze Map Editor|Update Requests]] layer. *Process and resolve map errors/problems as shown on the [[Map Problems in Waze Map Editor|Map Problems]] layer. *Make changes to the map when road construction projects start and finish by maintaining new geometry, adding or deleting roads and disconnecting and re-connecting ramps. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Act as a mentor to other editors, offering advice in both the forums and when you see improper edits on the map. == How to Become an Area Manager == The position of Area Manager is by appointment. To become an area manager, you must meet the prerequisites and then submit your application. Prospective Area Managers should already... *have at least a few months of experience editing the Waze maps regularly. *have read and followed the guidelines for mapping found in the wiki, starting at the Waze Map Editing page. *have completed at least 5000 quality edits. *have a real Waze username which does not start with usa_ or world_. *have their state and/or country in their forum profile. *have forum PMs enabled and associated with a valid and verifiable email address. *be active in the Waze forums, asking questions, and even providing guidance for newer editors, if possible. *know who their regional coordinator is. (Knowing the correct answer to this is a strong indicator as to how much reading an applicant has done of the forums and Wiki). === Required Reading === Before applying to become an AM, you will be expected to have read the following wiki pages and forums. '''Wiki''' *[[Map Editing Quick-start Guide]] *[[Best map editing practice]] *[[Map Editing Tips and Hints]] *[[Waze Map Editor|Waze Map Editor]] and all the [[Waze Map Editor#Editing Manual|Editing Manual]] links therein ''Be sure to also find and read the editing guidelines specific to your country.'' '''Forum''' You should also read these two forums and know where the Unlock Request is located *[http://www.waze.com/forum/viewtopic.php?f=636&t=45237%7C READ ME FIRST! General forum guidelines] *[http://www.waze.com/forum/viewtopic.php?t=32072%7C Unlock Request Instructions] *[http://www.waze.com/forum/viewforum.php?f=265%7C Unlock Request] == Area Manager application process == ==== Identifying your area ==== Before you head off to submit your application for AM, use the [[Map Editing (new Editor)|Waze Map Editor]], position the map and set the zoom level to show the area you want to manage. Make a [[Map Editing (new Editor)#Permalink|Permalink]] of the area and copy the address from the address bar in your browser. === Area Manager territory === *More than one Area Manager can manage the same area. *Areas can overlap, be smaller or larger. *You can also be the AM for more than one area. Notice the green area of the map has four managers. [[File:AreaManagerLayer.png]] === The application === If you would like to become an Area Manager, or expand your existing area, you will need to '''complete the appropriate application form for your country'''. The following countries have a self management system and requests will be approved by country managers or coordinators. ''Please go to the relevant [http://www.waze.com/forum/viewforum.php?f=19 country forum] to find the appropriate application form:'' *[http://www.waze.com/forum/viewforum.php?f=645 USA] *[http://www.waze.co.il/forum/viewforum.php?f=38 Israel] *[http://www.waze.com/forum/viewforum.php?f=55 United Kingdom] *[http://www.waze.com/forum/viewforum.php?f=25 Hungary] *[http://world.waze.com/forum/viewforum.php?f=26 Spain] *[http://www.waze.com/forum/viewforum.php?f=279 Malaysia] / [http://www.waze.com/forum/viewforum.php?f=191 Singapore] / Brunei *[http://www.waze.com/forum/viewtopic.php?f=331&t=29288 Brazil] *[http://www.waze.com/forum/viewforum.php?f=20 Italy] *[http://www.waze.com/forum/viewforum.php?f=700 Belgium] / [http://www.waze.com/forum/viewforum.php?f=21 The Netherlands] / [http://www.waze.com/forum/viewforum.php?f=381 Luxembourg] *[http://www.waze.com/forum/viewforum.php?f=24 Germany / Austria / Switzerland] *[http://www.waze.com/forum/viewforum.php?f=34 France] *[http://www.waze.com/forum/viewforum.php?f=440 Chile] *[http://www.waze.com/forum/viewforum.php?f=611 Portugal] *[http://www.waze.com/forum/viewforum.php?f=22 Czech republic & Slovakia] *[http://www.waze.com/forum/viewforum.php?f=465 Mexico] *[http://www.waze.com/forum/viewforum.php?f=33 Sweden] *[http://www.waze.com/forum/viewtopic.php?f=359&t=88599 Paraguay] *[http://www.waze.com/forum/viewforum.php?f=309 Philippines] *[http://www.waze.com/forum/viewforum.php?f=171 India] *[http://www.waze.com/forum/viewforum.php?f=120 Romania] *[http://world.waze.com/forum/viewtopic.php?f=56&t=59583 Australia] *[http://www.waze.com/forum/viewtopic.php?f=501&t=64255 Costa Rica] '''For all other countries''', AM requests should be [http://docs.google.com/a/waze.com/spreadsheet/viewform?formkey=dGl6TVF2bzFtdHRWUDVzR3N5TllZanc6MA#gid=0 submitted via this form] and will be handled directly by Waze support. == Area Manager Links == *[[Waze Map Editor|Map Editing]] *[[Best map editing practice]] *[[Area Manager: Diagnosis]] *[[Area Manager: Tips and Tricks]] <!-- * [[Area Manager: YouTube Training Videos]]--> *[[Area Manager: How to edit wiki pages]] *[[Known issues]] *Road Types: [[Road Types (USA)|(USA)]], [[Road Types India|India]] *[[Junction Style Guide|Junction Style Guide]] *[[Area Manager: 101]] == List of Area Managers == See [http://bit.ly/WazeAMs List of Area Managers and their preferred contact details]. 9a8074fcb28eec97e62a2857a3898c0c71ade811 10 50 160 2014-07-26T17:45:44Z Kentsmith9 25 created disabmiguation wikitext text/x-wiki '''Style guide''' may refer to: * Style guide, for map editing see [[:Category:Style Guides]] * Style guide, for [[Help:Wiki_editing|Wiki editing]] {{Disambig}} 17cd86865ed820e98f0165872e016475adbc2c03 0 96 668 667 2014-07-26T23:18:53Z Kentsmith9 25 updated link wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [https://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_restrictions#Unlocking_an_object_above_your_rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 780a37a58817af152e1f9d38e708bab583498a6d 669 668 2014-07-26T23:35:31Z Kentsmith9 25 https wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map_Editing_Quick-start_Guide#Delete_a_Junction|deleting a junction]] for more information. See also [[Creating_and_Editing_street_segments#Road_elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road_types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing_penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating_and_Editing_street_segments#Road_Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing_restrictions#Unlocking_an_object_above_your_rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning_on_possible_lack_of_accuracy_in_aerial_images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[classification_of_crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 1e17216c4f0853c77bf522e5d277886406b8c9af 670 669 2014-07-28T00:51:05Z Kentsmith9 25 fixed double redirect wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type. * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]]. * U-turns are required to properly make turns that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] c6af67cfba8200674b5ec564e8023a21fa9eca62 672 671 2014-09-15T20:53:49Z Kentsmith9 25 /* {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) */ Per forum wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type, * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], or * U-turns are required to properly make turns from public drivable road types that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 54f16035ab4caf78c4beb76f908a477517530ebb 673 672 2014-10-26T15:26:34Z PesachZ 26 /* Handling Restricted Lanes */ added link to dedicated page wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type, * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], or * U-turns are required to properly make turns from public drivable road types that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes, lanes that are open (or change direction) at certain times of day, etc.. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with so far is to leave these segments' directionality as whatever their native would be. If it's a set of lanes which switch directionality at times, set it to 2-way. If it is always a 1-way, set it as such. In order to make it less likely that Waze will route anyone onto these express lanes, HOV lanes, etc., any ramps connecting these segments to regular freeway or street segments should be set as '''Parking Lot road type''' and turns onto the parking lot road segments and the freeway or highway segments are '''Disallowed'''. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. {{details|Carpool, HOV, Transit lanes}} ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] f8cd357ebb7c348e85b2e005ea58c87429317b5a 674 673 2014-10-26T17:33:50Z PesachZ 26 /* Handling Restricted Lanes */ updated to current information on capabilties for TBTR, and new HOV guidelines wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type, * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], or * U-turns are required to properly make turns from public drivable road types that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as well. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. {{details|Carpool, HOV, Transit lanes}} ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === It is not recommended to lock segments in residential neighborhoods. Locking should be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 49626cc442c5c8895d870a5fd9282fc510b25f7f 675 674 2014-10-26T19:17:37Z PesachZ 26 /* Locking Segments */ updated to reflect locking standards in some regions as per https://www.waze.com/forum/viewtopic.php?p=935815#p935815 wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === Generally only freeways or major highways are split into two one-way roads. When initially reviewing whether to split or "un-split" (merge back together) a roadway, consider these points first: # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> Some formal guidelines - '''A road should be split when:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type, * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], or * U-turns are required to properly make turns from public drivable road types that are blocked by a median. '''A road should ''not'' be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as well. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. {{details|Carpool, HOV, Transit lanes}} ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === In some regions there are locking rank standards applied based on road type. In these regions all roads of a certain type are locked to a minimum rank, and should be locked even in residential areas. Check [[Template:Countries|your local wiki]] for your local standards to see if these apply in your editing area. Locking should otherwise be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves two purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] ecf96090f6bd28bbf696846db35360138d811af4 679 678 2014-12-10T16:25:41Z Kentsmith9 25 /* {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) */ Note to update glossary wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === {{anchor|When (Not) to Split a Two-Way Road}}When to Split a Two-Way Road (and when not to) === <!-- After this anchor is updated to the new term, update the glossary to link back here for the entry [[Glossary#Dual carriageway]] --> Generally, a road should be undivided unless it meets any of the requirements for dividing a road. When initially reviewing whether to split (divide) or "un-split" (merge back together) a roadway, consider these points first: # The default setting for any roadway is a single 2-way segment, not a pair of divided 1-way segments. Dividing a roadway carries with it the burden of proof. # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before splitting/un-splitting. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being split and "un-split". For example, if most of the road is clearly split and only parts would be considered a single two-way road, consider leaving it all split. The same goes for the opposite situation. <br/> '''A road may be split when <u>any</u> of the following conditions are met:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type, * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], * multiple houses or businesses with no off-street parking are located directly on the street but are not accessible from the opposite direction of travel due to lengthy median, obstruction, or traffic control signage, or * U-turns are required to properly make turns from public drivable road types that are blocked by a median. '''A road should <u>not</u> be split when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Splitting this type of road created problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a left turn/u-turn at any point along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. {{clear}} Remember that splitting and unsplitting roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a split road. Consider every aspect of routing, and carefully examine each junction before splitting or unsplitting. Regardless of whether you're splitting or unsplitting, remember that you might cause more problems than you solve and you might have to put it back the way it was before. === How to "Un-Split" two One-Way Roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before splitting a road in the first place. And then think some more. When you come across a road in your area that has been split, but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way split roads UNLESS there are Update Requests related to the road caused by it being split. {{Red|The process to undivide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:UndivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:UndivideRd2.jpg]] 2. Disconnect both segments from one side of the section being undivided. It is best to disconnect alternate ends of each segment as shown. [[File:UndivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:UndivideRd4.jpg]] The following video was recorded by an editor merging two split one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as well. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. {{details|Carpool, HOV, Transit lanes}} ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === In some regions there are locking rank standards applied based on road type. In these regions all roads of a certain type are locked to a minimum rank, and should be locked even in residential areas. Check [[Template:Countries|your local wiki]] for your local standards to see if these apply in your editing area. Locking should otherwise be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves three purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. *it prevents the Waze client from routing thru-traffic along the parking lot segments. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area. Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using two segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 1556946396b626c08bec840756a5c0b7642622b8 10 51 167 166 2014-07-28T01:00:00Z Kentsmith9 25 fixed double redirect wikitext text/x-wiki '''Toll''' may refer to: * [[Best map editing practice#Toll roads|Toll roads]], the best map editing practice for when to create them * [[Creating and editing road segments#Toll road|Toll road]], the check box in the Waze Map Editor * [[Avoid toll roads]], the setting in the Waze client app to route without using toll roads {{Disambig}} db834bca3e4a58230e0c53888dd746852b8b48a6 168 167 2014-08-14T16:19:41Z Kentsmith9 25 typo wikitext text/x-wiki '''Toll''' may refer to: * [[Best map editing practice#Toll roads|Toll roads]], the best map editing practice for when to create them * [[Creating and editing road segments#Toll Road||Toll road]], the check box in the Waze Map Editor * [[Avoid toll roads]], the setting in the Waze client app to route without using toll roads {{Disambig}} 762d676b7d1a52942fc9eb22950579dd692c26c0 169 168 2014-08-14T16:19:57Z Kentsmith9 25 typo wikitext text/x-wiki '''Toll''' may refer to: * [[Best map editing practice#Toll roads|Toll roads]], the best map editing practice for when to create them * [[Creating and editing road segments#Toll Road|Toll road]], the check box in the Waze Map Editor * [[Avoid toll roads]], the setting in the Waze client app to route without using toll roads {{Disambig}} cf35782c60dcecee36548de9712d264542d2fdaf 0 22 61 60 2014-07-28T03:52:18Z Kentsmith9 25 fixed double redirect wikitext text/x-wiki #REDIRECT [[Waze symbols]] 694ccc99341800635fc49c19be05bfab9495293e 10 75 375 374 2014-07-28T06:23:26Z Kentsmith9 25 updated links wikitext text/x-wiki <span style="color: red;">''The specific details of the Area Manager role are currently under review within the Waze community. Some of the information below is currently out of date. Please review the [http://www.waze.com/forum forums] for more information. Once the role changes are finalized, this section will be updated as required.''</span> <br/>An Area Manager, AM for short, is a Waze community member (a user) who wishes to take an active and proactive role in maintaining specific areas of the Waze map. How deeply involved and how much time an Area Manager spends maintaining the Waze map varies greatly. Duties of an Area Manager include, but not necessarily limited to: *Respond to and correct user update requests on the [[Update Requests in Waze Map Editor|Update Requests]] layer. *Process and resolve map errors/problems as shown on the [[Map Problems in Waze Map Editor|Map Problems]] layer. *Make changes to the map when road construction projects start and finish by maintaining new geometry, adding or deleting roads and disconnecting and re-connecting ramps. *Maintain speed and red-light cameras, processing reports of devices from Waze drivers. *Act as a mentor to other editors, offering advice in both the forums and when you see improper edits on the map. == How to Become an Area Manager == The position of Area Manager is by appointment. To become an area manager, you must meet the prerequisites and then submit your application. Prospective Area Managers should already... *have at least a few months of experience editing the Waze maps regularly. *have read and followed the guidelines for mapping found in the wiki, starting at the Waze Map Editing page. *have completed at least 5000 quality edits. *have a real Waze username which does not start with usa_ or world_. *have their state and/or country in their forum profile. *have forum PMs enabled and associated with a valid and verifiable email address. *be active in the Waze forums, asking questions, and even providing guidance for newer editors, if possible. *know who their regional coordinator is. (Knowing the correct answer to this is a strong indicator as to how much reading an applicant has done of the forums and Wiki). === Required Reading === Before applying to become an AM, you will be expected to have read the following wiki pages and forums. '''Wiki''' *[[Map Editing Quick-start Guide]] *[[Best map editing practice]] *[[Map Editing Tips and Hints]] *[[Waze Map Editor]] and all the [[Editing manual]] links therein ''Be sure to also find and read the editing guidelines specific to your country.'' '''Forum''' You should also read these two forums and know where the Unlock Request is located *[http://www.waze.com/forum/viewtopic.php?f=636&t=45237%7C READ ME FIRST! General forum guidelines] *[http://www.waze.com/forum/viewtopic.php?t=32072%7C Unlock Request Instructions] *[http://www.waze.com/forum/viewforum.php?f=265%7C Unlock Request] == Area Manager application process == ==== Identifying your area ==== Before you head off to submit your application for AM, use the [[Waze Map Editor]], position the map and set the zoom level to show the area you want to manage. Make a [[Waze Map Editor#Permalink|Permalink]] of the area and copy the address from the address bar in your browser. === Area Manager territory === *More than one Area Manager can manage the same area. *Areas can overlap, be smaller or larger. *You can also be the AM for more than one area. Notice the green area of the map has four managers. [[File:AreaManagerLayer.png]] === The application === If you would like to become an Area Manager, or expand your existing area, you will need to '''complete the appropriate application form for your country'''. The following countries have a self management system and requests will be approved by country managers or coordinators. ''Please go to the relevant [http://www.waze.com/forum/viewforum.php?f=19 country forum] to find the appropriate application form:'' *[http://www.waze.com/forum/viewforum.php?f=645 USA] *[http://www.waze.co.il/forum/viewforum.php?f=38 Israel] *[http://www.waze.com/forum/viewforum.php?f=55 United Kingdom] *[http://www.waze.com/forum/viewforum.php?f=25 Hungary] *[http://world.waze.com/forum/viewforum.php?f=26 Spain] *[http://www.waze.com/forum/viewforum.php?f=279 Malaysia] / [http://www.waze.com/forum/viewforum.php?f=191 Singapore] / Brunei *[http://www.waze.com/forum/viewtopic.php?f=331&t=29288 Brazil] *[http://www.waze.com/forum/viewforum.php?f=20 Italy] *[http://www.waze.com/forum/viewforum.php?f=700 Belgium] / [http://www.waze.com/forum/viewforum.php?f=21 The Netherlands] / [http://www.waze.com/forum/viewforum.php?f=381 Luxembourg] *[http://www.waze.com/forum/viewforum.php?f=24 Germany / Austria / Switzerland] *[http://www.waze.com/forum/viewforum.php?f=34 France] *[http://www.waze.com/forum/viewforum.php?f=440 Chile] *[http://www.waze.com/forum/viewforum.php?f=611 Portugal] *[http://www.waze.com/forum/viewforum.php?f=22 Czech republic & Slovakia] *[http://www.waze.com/forum/viewforum.php?f=465 Mexico] *[http://www.waze.com/forum/viewforum.php?f=33 Sweden] *[http://www.waze.com/forum/viewtopic.php?f=359&t=88599 Paraguay] *[http://www.waze.com/forum/viewforum.php?f=309 Philippines] *[http://www.waze.com/forum/viewforum.php?f=171 India] *[http://www.waze.com/forum/viewforum.php?f=120 Romania] *[http://world.waze.com/forum/viewtopic.php?f=56&t=59583 Australia] *[http://www.waze.com/forum/viewtopic.php?f=501&t=64255 Costa Rica] '''For all other countries''', AM requests should be [http://docs.google.com/a/waze.com/spreadsheet/viewform?formkey=dGl6TVF2bzFtdHRWUDVzR3N5TllZanc6MA#gid=0 submitted via this form] and will be handled directly by Waze support. == Area Manager Links == *[[Waze Map Editor|Map Editing]] *[[Best map editing practice]] *[[Area Manager: Tips and Tricks]] <!-- * [[Area Manager: YouTube Training Videos]]--> *[[Help:Wiki editing]] *[[Known issues]] *Road Types: [[Road types/USA|(USA)]], [[Road Types India|India]] *[[Junction Style Guide]] *[[Area Manager: 101]] 4328c65e507652f59cbe9f5ef2fa60f956f4fa02 10 57 181 2014-07-28T08:08:59Z Kentsmith9 25 #REDIRECT [[Trigger (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Trigger (disambiguation)]] b78ffb6ce032295a8b98d7e67d52d5e247311723 2 56 179 2014-07-28T08:18:05Z Kentsmith9 25 created disabmiguation wikitext text/x-wiki '''Trigger''' may refer to: * Trigger, some map edits will force a [[Tile update#Trigger updates|tile update]] * Trigger, when Waze servers [[Timeline of updating process#Automatic road updates by Waze|make changes to unedited roads]], like directionality * Trigger, activating a red light or speed [[Cameras|Camera]] while driving * Trigger, when Waze servers automatically identify [[Map Problems in Waze Map Editor|map problems]] {{Disambig}} d1d25166217b045828738811379b660629fdb8a1 10 66 11851 11850 2014-08-03T21:33:14Z Kentsmith9 25 Added Chile wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:xx.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Turkey]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> e61d9eadd871a31e44500f17497284c852e7da2f 11852 11851 2014-08-03T21:36:15Z Kentsmith9 25 rename wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] [http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Turkey]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 4272804ec4181c59bef788ef1c2dfa826ee9a8aa 11853 11852 2014-08-03T22:47:00Z Kentsmith9 25 hid external link arrow wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Turkey]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 0eda28bf1c6c7814b897196caaf8ead2ff77dfc4 11854 11853 2014-09-09T07:00:33Z PesachZ 26 Turkey wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Türkiye|Turkey (Türkiye)]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 55810a073230d3ffd55c9bcb1ec597724477e78c 11855 11854 2014-10-10T05:48:01Z Kentsmith9 25 Added Iceland wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|България (Bulgaria)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|中国 (China)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:De.png]] [[Deutschland|Deutschland (Germany)]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Es.png]] [[España|España (Spain)]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:Ic.png]] [[Iceland]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:It.png]] [[Italy]] <li>[[Image:Kr.png|25px]] [[Korea|대한민국 (Korea)]] <li>[[image:Japan-flag.jpg||25px]] [[日本|日本 (Japan)]] <li>[[Image:Lv.png]] [[Latvija|Latvia]] <li>[[Image:Lux.gif]] [[Luxembourg|Lëtzebuerg (Luxembourg)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuviškai (Lithuania)]] <li>[[Image:Hu.png]] [[Hungary|Magyarország (Hungary)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Oesterreich.png]] [[Österreich|Österreich (Austria)]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.png]] [[Switzerland]] <li>[[Image:Turkey.png]] [[Türkiye|Turkey (Türkiye)]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 84591ea3d20e171da4d5ea3b0c0520e78dc1fe3f 10 28 11364 11363 2014-08-03T21:34:17Z Kentsmith9 25 Added Chile wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:xx.png]]&nbsp;[[Chile]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Na.png|25px]]&nbsp;[[Namibia]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Norway_flag.png]]&nbsp;[[Norway]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Turkey]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> bdb903bfed9d8865051881429ef0375a8cb62087 11365 11364 2014-08-03T21:36:36Z Kentsmith9 25 rename wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cl.png]]&nbsp;[[Chile]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Na.png|25px]]&nbsp;[[Namibia]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Norway_flag.png]]&nbsp;[[Norway]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Turkey]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> faa2118811d6b9ccb1f02a115a362cee43e5b32b 11366 11365 2014-09-09T06:59:52Z PesachZ 26 Turkey wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cl.png]]&nbsp;[[Chile]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Na.png|25px]]&nbsp;[[Namibia]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Norway_flag.png]]&nbsp;[[Norway]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Türkiye|Turkey (Türkiye)]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> 70427225dd63cee1258e3b1ecd314f2ad7d6ea19 11367 11366 2014-10-10T05:49:36Z Kentsmith9 25 Added Iceland wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cl.png]]&nbsp;[[Chile]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany (Deutschland)]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary (Magyarország)]] *[[Image:Ic.png]]&nbsp;[[Iceland]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg (Lëtzebuerg)]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Na.png|25px]]&nbsp;[[Namibia]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Norway_flag.png]]&nbsp;[[Norway]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.png]]&nbsp;[[Switzerland]] *[[Image:Turkey.png]]&nbsp;[[Türkiye|Turkey (Türkiye)]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> 8a04a4b3f73705f4be83a4cc3c8b7e49af31ae3b 10 67 11873 2014-08-03T21:44:02Z Kentsmith9 25 Initial template creation wikitext text/x-wiki <span class="plainlinks">[{{{1|http://www.testpage.com External Link Example}}}]</span><noinclude>{{doc}}</noinclude> f255e3daaae762128e4329935e686a1ac0d37651 11874 11873 2014-08-03T22:18:45Z Kentsmith9 25 error trapping wikitext text/x-wiki <span class="plainlinks">[{{{1|http://www.testpage.com Do Not Include <nowiki>[]</nowiki>}}}]</span><noinclude>{{doc}}</noinclude> 8680dbfb390ed132387ba1c536e1fcf24e1eb9fd 11875 11874 2014-08-03T22:45:06Z Kentsmith9 25 updated doc wikitext text/x-wiki <span class="plainlinks">[{{{1|http://www.testpage.com Do not include <nowiki>[]</nowiki> and replace {{u|'''&#61;'''}} with {{u|'''&amp;#61;'''}}}}}]</span><noinclude>{{doc}}</noinclude> 13a21a5556a2d71e3b78f04d40191ca1820d85ed 0 30 95 94 2014-08-28T14:11:17Z PesachZ 26 added Traffic Locks wikitext text/x-wiki '''Lock''' may refer to: * [[Editing_rank#Locked_segments|Locked segments]], how they work and how to unlock them ** [[Traffic locks|Automatic or Traffic Locks]] * [[Best map editing practice#Locking Segments|Locking segments]], the best map editing practice * Lock level, setting the security level of a road in the Waze Map Editor [[Map_Editor_Interface_and_Controls#General_Tab|General tab]] * Lock (Landmark), setting on Waze Map Editor when [[Map_Editor_Interface_and_Controls#Tabs_when_a_landmark_is_selected|editing a landmark]] {{Disambig}} cead777b295365156319b46c6f9f8298c6de7fd7 96 95 2014-08-28T21:19:17Z Kentsmith9 25 updated links; resorted list; adjusted language wikitext text/x-wiki '''Lock''' may refer to: * [[Map_Editor_Interface_and_Controls#General_Tab|Lock rank]], setting the security level of a road in the Waze Map Editor * [[Traffic locks]], the automatic segment lock process based on traffic volume * [[Best map editing practice#Locking Segments|Locking segments]], map editing best practices * [[Editing_restrictions#Unlocking_an_object_above_your_rank|Unlocking segments]] above your rank * [[Map_Editor_Interface_and_Controls#Tabs_when_a_landmark_is_selected|Lock (Place/Landmark)]], when editing a place/landmark in Waze Map Editor {{Disambig}} 4b14145f0f01592479e1b43eaf9f467db86182d3 0 6 12 2014-09-02T23:17:15Z PesachZ 26 created angle DAB wikitext text/x-wiki '''Angle''' may refer to: * [[Junction angle]] - the angle between any two segments connected at a junction. * [[Interactive_junction_instruction_algorithm#Turn angle|Turn angle]] - the supplementary angle to the junction angle between any two segments connected at a junction. * [[Interactive_junction_instruction_algorithm#Turn angle#roundabout angle|Roundabout angle]] - the relative position in compass degrees where a segment connects to the roundabout. {{Disambig}} 08a4c3a5d7037060ca5c29d05c4d4adabf04562c 13 12 2014-09-02T23:21:05Z PesachZ 26 fixed link wikitext text/x-wiki '''Angle''' may refer to: * [[Junction angle]] - the angle between any two segments connected at a junction. * [[Interactive_junction_instruction_algorithm#Turn angle|Turn angle]] - the supplementary angle to the junction angle between any two segments connected at a junction. * [[Interactive_junction_instruction_algorithm#roundabout angle|Roundabout angle]] - the relative position in compass degrees where a segment connects to the roundabout. {{Disambig}} 48fb4b1b2696c9767d99ea2363ba2be79f3125ed 14 13 2014-09-02T23:49:35Z PesachZ 26 wikitext text/x-wiki '''Angle''' may refer to: * [[Junction angle]] - the angle between any two segments connected at a junction. * [[Interactive_junction_instruction_algorithm#Turn angle|Turn angle]] - the supplementary angle to the junction angle between any two segments connected at a junction. * [[Interactive_junction_instruction_algorithm#roundabout angle|Roundabout angle]] - the relative position in compass degrees where a segment connects to a roundabout. {{Disambig}} a76a881f35d1c312517b8703196622afe7d17f5b 15 14 2014-09-03T15:30:56Z Kentsmith9 25 Adjusted format to DAB style wikitext text/x-wiki '''Angle''' may refer to: * [[Junction angle]], between two segments connected at a junction * [[Interactive_junction_instruction_algorithm#Turn angle|Turn angle]], the supplementary angle to the junction angle * [[Interactive_junction_instruction_algorithm#roundabout angle|Roundabout angle]], the relative position in compass degrees where a segment connects {{Disambig}} ac1311044032c18cee3f6bf279afb87ebd0a300b 0 7 17 2014-09-02T23:23:22Z PesachZ 26 Redirected page to [[Angle (disambiguation)]] wikitext text/x-wiki #REDIRECT [[Angle (disambiguation)]] 3a4a8f1b5525b725c5dfd4d7e81b9b496e417b2b 10 58 11746 11745 2014-11-15T09:17:22Z Kentsmith9 25 Added new editor.png wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox warning yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | neweditor = Mbox new editor.png | mail = Mbox mail.png | forum = Gnome-system-users.svg.png | cleanup = Edit-clear.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> {{Documentation|content=This subtemplate supports the default values of {{tl|Mbox}}. It should not be altered without review from a Wiki Expert. Contact one through the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion forum.]}} <!-- This category is only for the template itself --> [[Category:Template:Mbox]] </noinclude> 1f1d23d1e424138574542a8c93dcc02b28d622ac 0 21 54 53 2014-11-25T02:25:07Z Kentsmith9 25 typo wikitext text/x-wiki '''Icon''' links directly to: * [[Waze symbols]], client app icons for alert, moods (other drivers), ranks, and candy '''Icon''' may also refer to: * Forum icon, (or [[Your_Rank_and_Points#Forum_badges|Forum badge]]) appears in right pane of an editor's forum post * Park icon, (or [[Nearing_destination|parking pin]]) to mark the location of your vehicle * [[Map_Editing_Quick-start_Guide#Turn icons|Turn icon]], the turn indicators in the Waze Map Editor {{Disambig}} 6670e22cd2405e530ff396050aad5170e9c52f61 55 54 2014-11-25T02:28:09Z Kentsmith9 25 Map editing icons wikitext text/x-wiki '''Icon''' links directly to: * [[Waze symbols]], client app icons for alert, moods (other drivers), ranks, and candy '''Icon''' may also refer to: * Forum icon, (or [[Your_Rank_and_Points#Forum_badges|Forum badge]]) appears in right pane of an editor's forum post * Park icon, (or [[Nearing_destination|parking pin]]) to mark the location of your vehicle * [[Map_Editing_Quick-start_Guide#Turn icons|Turn icon]], the turn indicators in the Waze Map Editor * [[Map_Editor_Interface_and_Controls|Map editing icons]], buttons for making changes to the map {{Disambig}} cfb3b86825b7196913e0b9bdf1e9e8d31c65a74d 10 68 11883 11882 2014-12-09T12:59:43Z NetHunter 1 1 revision wikitext text/x-wiki &#123;&#123;[[Template:{{{1}}}|{{{1}}}]]&#125;&#125;<noinclude> {{documentation}} <!-- Categories go on the /doc subpage and interwikis go on Wikidata. --> </noinclude> 91be693cd63410db06fc933eddb412ba433564dc 10 45 146 2014-12-09T19:39:31Z Kentsmith9 25 #REDIRECT [[Split_(disambiguation)]] wikitext text/x-wiki {{construction | contact = http://www.waze.com/forum/viewtopic.php?f=276&t=120314 | contacttype = forum | draft = yes | revision = yes }} '''Split''' may refer to: * Split road, two separate divided roads with a median; a dual carriageway * Splitting a road, the act of dividing a road into two adjacent one-way roads * Unsplitting a road, the act of replacing two adjacent one-way roads into a single two-way road * Split a segment, to cut one segment into two segments * Road split, a point where a single road diverges into two directions {{Disambig}} 239a31beb274e17ca1ccce5d87cd35c668b31c01 147 146 2014-12-22T23:09:07Z PesachZ 26 added links, sorted by length, removed draft from construction box wikitext text/x-wiki {{construction | contact = http://www.waze.com/forum/viewtopic.php?f=276&t=120314 | contacttype = forum | draft = no | revision = yes }} '''Split''' may refer to: * [[Map_Editing_Quick-start_Guide#Splitting_a_segment|Split a segment]], to cut one segment into two segments * [[Junction_Style_Guide/Interchanges#Freeway.2Fhighway_splits|Road split]], a point where a single road diverges into two directions (The MUTCD definition of ''split'') * Split road, two separate divided roads with a median; a dual carriageway * [[Best_map_editing_practice#When_to_Split_a_Two-Way_Road_.28and_when_not_to.29|Splitting a road]], the act of dividing a road into two adjacent one-way roads * [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Unsplitting a road]], the act of replacing two adjacent one-way roads into a single two-way road {{Disambig}} 9f3cd4e519afaf0955a2fa52197f6c2c3b0f003b 148 147 2014-12-22T23:10:08Z PesachZ 26 added deprecated box wikitext text/x-wiki {{construction | contact = http://www.waze.com/forum/viewtopic.php?f=276&t=120314 | contacttype = forum | draft = no | revision = yes }} {{mbox | type = notice | text = The term '''split''' has been deprecated in the Wiki since it has too many meanings and alternate meanings are better representations. }} '''Split''' may refer to: * [[Map_Editing_Quick-start_Guide#Splitting_a_segment|Split a segment]], to cut one segment into two segments * [[Junction_Style_Guide/Interchanges#Freeway.2Fhighway_splits|Road split]], a point where a single road diverges into two directions (The MUTCD definition of ''split'') * Split road, two separate divided roads with a median; a dual carriageway * [[Best_map_editing_practice#When_to_Split_a_Two-Way_Road_.28and_when_not_to.29|Splitting a road]], the act of dividing a road into two adjacent one-way roads * [[Best_map_editing_practice#How_to_.22Un-Split.22_two_One-Way_Roads|Unsplitting a road]], the act of replacing two adjacent one-way roads into a single two-way road {{Disambig}} d95259195e1056cb7ef2606a82f5027206f05fee 0 12 10702 2014-12-18T11:52:40Z BellHouse 29 Erste Demo-Version wikitext text/x-wiki <big>'''Organisation DACH'''</big> Diese Seite gibt eine Übersicht der Country Manager (CM) der DACH-Länder Deutschland, Österreich und Schweiz. == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | top_gun_de || 5 || X || X || X || || |- | BaseMapFrieder || 5 || || || || || X |- | BellHouse || 6 || || || X || X || |- | Durango48 || 6 || || X|| X || X || |- | gordonski || 5 || || || X || || |- | Gugi1968 || 5 || || || || || |- | Hallenbach || 5 || || || || || X |- | MarcoSaxonia || 5 || || || || || X |- | Mesonus || 5 || || || || || |- | Mynios || 5 || || X || X || || |- | Raccoon1 || 5 || || || || || |- | Snake68 || 5 || || || X|| X || |- | Tilonius || 6 || || || X || || |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} d755ad9f07eb2dd433edfa072faf1f9268e8cfcd 10703 10702 2014-12-18T12:05:09Z BellHouse 29 Erklärung der Abkürzungen wikitext text/x-wiki <big>'''Organisation DACH'''</big> Diese Seite gibt eine Übersicht der Country Manager (CM) der DACH-Länder Deutschland, Österreich und Schweiz. Verwendete Abkürzungen: ;GC: Global Champ<br> ;LC: Local Champ<br> ;AMS: Autonomous Management System (deutsch: Selbstverwaltung)<br> ;SME: Social Media Expert<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | top_gun_de || 5 || X || X || X || || |- | BaseMapFrieder || 5 || || || || || X |- | BellHouse || 6 || || || X || X || |- | Durango48 || 6 || || X|| X || X || |- | gordonski || 5 || || || X || || |- | Gugi1968 || 5 || || || || || |- | Hallenbach || 5 || || || || || X |- | MarcoSaxonia || 5 || || || || || X |- | Mesonus || 5 || || || || || |- | Mynios || 5 || || X || X || || |- | Raccoon1 || 5 || || || || || |- | Snake68 || 5 || || || X|| X || |- | Tilonius || 6 || || || X || || |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} 719ed42cd509e429e90c75958f2c4858bdb40fd0 10704 10703 2014-12-18T12:07:53Z BellHouse 29 wikitext text/x-wiki <big>'''Organisation DACH'''</big> Diese Seite gibt eine Übersicht der Country Manager (CM) der DACH-Länder Deutschland, Österreich und Schweiz. Verwendete Abkürzungen: '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | top_gun_de || 5 || X || X || X || || |- | BaseMapFrieder || 5 || || || || || X |- | BellHouse || 6 || || || X || X || |- | Durango48 || 6 || || X|| X || X || |- | gordonski || 5 || || || X || || |- | Gugi1968 || 5 || || || || || |- | Hallenbach || 5 || || || || || X |- | MarcoSaxonia || 5 || || || || || X |- | Mesonus || 5 || || || || || |- | Mynios || 5 || || X || X || || |- | Raccoon1 || 5 || || || || || |- | Snake68 || 5 || || || X|| X || |- | Tilonius || 6 || || || X || || |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} a4c0156db536d49dcfc5a25a67165f67e57aef35 10705 10704 2014-12-18T12:08:37Z BellHouse 29 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Country Manager (CM) der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | top_gun_de || 5 || X || X || X || || |- | BaseMapFrieder || 5 || || || || || X |- | BellHouse || 6 || || || X || X || |- | Durango48 || 6 || || X|| X || X || |- | gordonski || 5 || || || X || || |- | Gugi1968 || 5 || || || || || |- | Hallenbach || 5 || || || || || X |- | MarcoSaxonia || 5 || || || || || X |- | Mesonus || 5 || || || || || |- | Mynios || 5 || || X || X || || |- | Raccoon1 || 5 || || || || || |- | Snake68 || 5 || || || X|| X || |- | Tilonius || 6 || || || X || || |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} 4c54d80b8a18175d952ce67c532471954263062e 10706 10705 2014-12-18T12:54:21Z BellHouse 29 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Country Manager (CM) der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | top_gun_de || 5 || X || X || X || || |- | BaseMapFrieder || 5 || || || || || X |- | BellHouse || 6 || || || X || X || |- | Durango48 || 6 || || X|| X || || |- | gordonski || 5 || || || X || || |- | Gugi1968 || 5 || || || || || |- | Hallenbach || 5 || || || || || X |- | MarcoSaxonia || 5 || || || || || X |- | Mesonus || 5 || || || || || |- | Mynios || 5 || || X || X || || |- | Raccoon1 || 5 || || || || || |- | Snake68 || 5 || || || X|| X || |- | Tilonius || 6 || || || X || || |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} 987e016e6235f41e549b99522f1ca909261378b2 10707 10706 2014-12-18T13:11:19Z BellHouse 29 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Country Manager (CM) der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! AMS !! SME |- | User1 || 5 || X || X || X || X || X |} b9017fd35e79724a42c62501f02dafd2b34b4995 10708 10707 2014-12-19T06:32:30Z BellHouse 29 CM-Spalte ergänzt wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !!AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} 51df91eac310eeed36289bf726a546d96ecd30cf 10710 10709 2015-01-13T08:27:46Z BellHouse 29 /* Deutschland */ PN->PM wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> AMS'': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PN''': Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} 9c919781337327999836a5e52be2ced48197061c 0 12 10711 10710 2015-01-13T08:28:38Z BellHouse 29 /* Verwendete Abkürzungen */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PN''': Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} 37914feed7b504d74c3203b99c38858c4bb60c04 10712 10711 2015-02-15T11:03:36Z BellHouse 29 /* Deutschland */ Liste eingefügt wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PN''': Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} 17848c4b3b68dd846038b074363d50e03c8789a6 10713 10712 2015-02-15T11:05:10Z BellHouse 29 /* Verwendete Abkürzungen */ Abkürzung PM wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME |- | User1 || 5 || X || X || X || X || X || X |} 07f07fc094609e9f186d344d01eb5a685543b8e3 10714 10713 2015-02-15T11:09:01Z BellHouse 29 PM-Spalte in AT und CH ergänzt wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1234567 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1234567 PM] |} 25dbad469889e402626acb9c8f8d564a4192b1a9 10715 10714 2015-02-15T11:10:12Z BellHouse 29 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} 66dfb2dabb0468719e17cba363053898f7d13080 10716 10715 2015-02-15T11:37:24Z BellHouse 29 /* Deutschland */ 2 neue LCs ergänzt wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} 92acc80fb5930721242ce01c9b4a25d8bad56e24 10717 10716 2015-02-16T12:42:54Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- {| {{table}} | align="center" style="background:#f0f0f0;"|'''User''' | align="center" style="background:#f0f0f0;"|'''Edit-Level''' | align="center" style="background:#f0f0f0;"|'''Koordinator''' | align="center" style="background:#f0f0f0;"|'''GC''' | align="center" style="background:#f0f0f0;"|'''LC''' | align="center" style="background:#f0f0f0;"|'''CM''' | align="center" style="background:#f0f0f0;"|'''AMS''' | align="center" style="background:#f0f0f0;"|'''SME''' | align="center" style="background:#f0f0f0;"|'''PM''' |- | argus-cronos||6||X||X||X||X||X||X||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 |- | svx-biker||6||||X||X||X||X||||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 |- | popel22||5||||||X||X||X||||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 |- | vince1612||5||||||X||X||X||X||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 |} 14a17b6fbbe4be45b83a444ef595cbff2d609223 10718 10717 2015-02-16T12:43:56Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} 92acc80fb5930721242ce01c9b4a25d8bad56e24 10719 10718 2015-02-16T12:47:46Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | align="center" style="background:#f0f0f0;"|'''User''' | align="center" style="background:#f0f0f0;"|'''Edit-Level''' | align="center" style="background:#f0f0f0;"|'''Koordinator''' | align="center" style="background:#f0f0f0;"|'''GC''' | align="center" style="background:#f0f0f0;"|'''LC''' | align="center" style="background:#f0f0f0;"|'''CM''' | align="center" style="background:#f0f0f0;"|'''AMS''' | align="center" style="background:#f0f0f0;"|'''SME''' | align="center" style="background:#f0f0f0;"|'''PM''' |- | argus-cronos||6||X||X||X||X||X||X||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 |- | svx-biker||6||||X||X||X||X||||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 |- | popel22||5||||||X||X||X||||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 |- | vince1612||5||||||X||X||X||X||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 |} |} 30fc7c8259266d803a49cd7ac6b74dff288fd26f 10720 10719 2015-02-16T12:50:08Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | align="center" style="background:#f0f0f0;"|'''User''' | align="center" style="background:#f0f0f0;"|'''Edit-Level''' | align="center" style="background:#f0f0f0;"|'''Koordinator''' | align="center" style="background:#f0f0f0;"|'''GC''' | align="center" style="background:#f0f0f0;"|'''LC''' | align="center" style="background:#f0f0f0;"|'''CM''' | align="center" style="background:#f0f0f0;"|'''AMS''' | align="center" style="background:#f0f0f0;"|'''SME''' | align="center" style="background:#f0f0f0;"|'''PM''' |- | argus-cronos||6||X||X||X||X||X||X||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 |- | svx-biker||6||||X||X||X||X||||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 |- | popel22||5||||||X||X||X||||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 |- | vince1612||5||||||X||X||X||X||https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 |} bc2f34b05401f20dd687157e04ca045bd2942f1f 10721 10720 2015-02-16T12:54:42Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | align="center" style="background:#f0f0f0;"|'''User''' | align="center" style="background:#f0f0f0;"|'''Edit-Level''' | align="center" style="background:#f0f0f0;"|'''Koordinator''' | align="center" style="background:#f0f0f0;"|'''GC''' | align="center" style="background:#f0f0f0;"|'''LC''' | align="center" style="background:#f0f0f0;"|'''CM''' | align="center" style="background:#f0f0f0;"|'''AMS''' | align="center" style="background:#f0f0f0;"|'''SME''' | align="center" style="background:#f0f0f0;"|'''PM''' |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |} 4b02a76df0aca0475e91bdd50155b9fbe858b335 10722 10721 2015-02-16T12:56:01Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | User1 || 5 || X || X || X || X || X || X || [https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=123456789 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |} 7c08d47a8b7aa81a8e49148db1ba90dbf2178e95 10725 10724 2015-02-17T07:27:30Z BellHouse 29 /* Deutschland */ +Raccoon_1 als AMS wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||5||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |} a6f536e737b94e16b6489765ccfc5908ed2570d1 10727 10726 2015-06-09T20:33:23Z Fuchserl 52 /* Österreich */ fuchserl -> CM wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |} af536dfc5e0f8bd01a6af6b826443b0544445f91 10728 10727 2015-09-04T10:06:15Z BellHouse 29 /* Deutschland */ BellHouse +GC wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |} c301774d9a28beedd63f711cca8fb0396cb72fc9 10731 10730 2015-10-04T08:58:29Z Fuchserl 52 /* Österreich */ pmex added wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | Pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |} 5de2cfea57adc1d2704a40653b8d7137ae5cd17d 10732 10731 2015-10-04T08:59:10Z Fuchserl 52 /* Österreich */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |} 16d23545d315776a75174b7d2d60a80d5e2c2a6c 10733 10732 2015-10-13T08:41:03Z Vince1612 23 Added popel22 as new GC wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |} 52b710efa7e81e8fbfdc2afd61df4b1d43b7ab58 10735 10734 2015-10-13T16:44:10Z Vince1612 23 Changed popel22 and vince1612 from lvl5 to lvl6 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |} 0b99bcbe507629dfd377dddde4126310816cb7f3 10736 10735 2015-11-10T21:03:07Z BellHouse 29 /* Deutschland */ tom-cat-67 als CM-D ergänzt wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |-|} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |} 61721d9575ddcaeea5d942e9bb8ee919b00be38b 10737 10736 2015-11-10T21:16:44Z BellHouse 29 Bugfix table DE wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |} 26c8736c648ce8c425edff529c549b727ae4115f 10738 10737 2015-11-28T00:16:10Z Vince1612 23 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- | argus-cronos||6||X||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | popel22||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |} 06d0e131a81981ffadacac8807f083096dfdd418 10739 10738 2015-12-05T19:33:44Z Vince1612 23 Changing coordinator info wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | ''argus-cronos (Inaktiv)''||''6''||||''X''||''X''||''X''||''X''||''X''||''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]'' |} 896f50428ee13896f7c9ad0224522b7cfae26f50 10740 10739 2015-12-05T19:43:14Z Vince1612 23 Nicer looking display for argus-cronos wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} b2a54558fa6113e26bb3925fb6d2f852dfa32cb8 10742 10741 2016-02-09T17:40:16Z Vince1612 23 Adding MattKo wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} cba7e72f6be1b1d5bdec3c13dbfc39c81515df46 10743 10742 2016-02-11T07:22:38Z BellHouse 29 /* Deutschland */ 2 neue CMs D (Jerec35, R66DE) wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} 471711493cfdd7bcfda26eb498c83430ed7dc705 10744 10743 2016-02-11T07:26:11Z BellHouse 29 /* Deutschland */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} 74a433f2f7e78817a18ac86b00045c620466f345 0 96 688 687 2015-03-22T14:19:37Z PesachZ 26 /* In Practice */ heading structure, section titles, and typos divided highways wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === Dividing and un-dividing divided highways === ==== {{anchor|When (Not) to Split a Two-Way Road|When to Split a Two-Way Road (and when not to)|When to divide a TwoWay Road (and when not to)}}When to divide a two-way road (and when not to) ==== <!-- After this anchor is updated to the new term, update the glossary to link back here for the entry [[Glossary#Dual carriageway]] --> Generally, a road should be un-divided unless it meets any of the requirements for dividing a road. When initially reviewing whether to divide or "un-divide" (merge back together) a roadway, consider these points first: # The default representation for any roadway is a single 2-way segment, even if the physical roadway is divided. Dividing a roadway carries with it the burden of proof that the change will improve the usability and/ or simplicity of the Waze map. # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before dividing/un-dividing. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being divided and 2-way. For example, if most of the road is clearly divided and only parts would be considered a single two-way road, consider leaving it all divided. If only a small portion seems better off divided, consider keeping it all 2-way. <br/> '''A road may be divided when <u>any</u> of the following conditions are met:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type, * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], * multiple houses or businesses with no off-street parking are located directly on the street but are not accessible from the opposite direction of travel due to lengthy median, obstruction, or traffic control signage, or * U-turns are required to properly make turns from public drivable road types that are blocked by a median. '''A road should <u>not</u> be divided when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a left turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. {{clear}} Remember that dividing and un-dividing roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a divided road. Consider every aspect of routing, and carefully examine each junction before dividing or un-dividing. Regardless of whether you're dividing or un-dividing, remember that you might cause more problems than you solve and you might have to put it back the way it was before. Also remember that dividing and un-dividing each cause loss of some traffic data, which can result in poor Waze routing. === {{anchor|How to "Un-Split" two One-Way Roads|How to "Un-divide" two One-Way Roads}}How to un-divide two one-way roads === Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before dividing a road in the first place. And then think some more. When you come across a road in your area that has been divided but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way roads UNLESS there are Update Requests related to the road caused by it being divided. {{Red|The process to un-divide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:un-divideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:un-divideRd2.jpg]] 2. Disconnect both segments from one side of the section being un-divided. It is best to disconnect alternate ends of each segment as shown. [[File:un-divideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:un-divideRd4.jpg]] The following video was recorded by an editor merging two one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as well. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. {{details|Carpool, HOV, Transit lanes}} ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. * ''see advanced topic on [[Time-based Tolls]] for mapping tolls that do not charge all the time.'' === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === In some regions there are locking rank standards applied based on road type. In these regions all roads of a certain type are locked to a minimum rank, and should be locked even in residential areas. Check [[Template:Countries|your local wiki]] for your local standards to see if these apply in your editing area. Locking should otherwise be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves three purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. *it prevents the Waze client from routing thru-traffic along the parking lot segments. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area (lots with entrances on both sides) or a single, flattened curve (lots that only have entrances/exits along a single road, such as for strip malls). Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using three segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 6d362af63ea4c1657f838a9f46fb1801ba2696d0 689 688 2015-03-22T14:22:09Z PesachZ 26 /* {{anchor|How to "Un-Split" two One-Way Roads|How to "Un-divide" two One-Way Roads}}How to un-divide two one-way roads */ fixed image links and header level wikitext text/x-wiki {{ReturnToEditingManual}} The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update requests]], set standards for [[Road types and names|labeling roads]], and a general [[FAQ]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits. If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum]. {{LocalGuidance}} <br/> {{TOC}} == Overall Goals == === Usability === When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed. === Simplicity === It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance. === Retention === As a result of people driving over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, that information is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is often better to "recycle". == In Practice == === Dividing and un-dividing divided highways === ==== {{anchor|When (Not) to Split a Two-Way Road|When to Split a Two-Way Road (and when not to)|When to divide a TwoWay Road (and when not to)}}When to divide a two-way road (and when not to) ==== <!-- After this anchor is updated to the new term, update the glossary to link back here for the entry [[Glossary#Dual carriageway]] --> Generally, a road should be un-divided unless it meets any of the requirements for dividing a road. When initially reviewing whether to divide or "un-divide" (merge back together) a roadway, consider these points first: # The default representation for any roadway is a single 2-way segment, even if the physical roadway is divided. Dividing a roadway carries with it the burden of proof that the change will improve the usability and/ or simplicity of the Waze map. # If a road is currently working with no problem reports, consider leaving it as is. # If the area has an Area Manager, consult with them before dividing/un-dividing. If the area does not have an Area Manager and after reviewing the formal guidelines below you are unsure which way to go, consider sending a [[Waze Map Editor#Permalink|permalink]] of the road to the [http://www.waze.com/forum/viewforum.php?f=8 map editing forums] to get additional feedback from other editors. # Try to avoid switching roads back and forth between being divided and 2-way. For example, if most of the road is clearly divided and only parts would be considered a single two-way road, consider leaving it all divided. If only a small portion seems better off divided, consider keeping it all 2-way. <br/> '''A road may be divided when <u>any</u> of the following conditions are met:''' * It is an Interstate Highway (USA) or other Limited Access Highway using the "Freeway" road type, * GPS tracks show a clearly definable and continuous gap (blank area) between the color-by-azimuth arrows at the 100m/500ft [[Map_Editor_Interface_and_Controls#Scale|zoom level]], * multiple houses or businesses with no off-street parking are located directly on the street but are not accessible from the opposite direction of travel due to lengthy median, obstruction, or traffic control signage, or * U-turns are required to properly make turns from public drivable road types that are blocked by a median. '''A road should <u>not</u> be divided when:''' * There is a curb or non-drivable median less than 5m wide between lanes of travel (see exceptions above). * The non-drivable median is interrupted by a cross segment at most intersections. * There is a center turn lane (any width) between directions of travel. Dividing this type of road creates problems when people turn from the middle lane because there is no road for the navigation to follow. * It is possible and legal to make a left turn/u-turn everywhere along the road * The objective is solely for visual appearance or to make the road match another visual source like Google Maps. {{clear}} Remember that dividing and un-dividing roads each comes with its own set of problems. Each situation is unique and some issues may be more manageable with a single two-way road, and some may work fine with a divided road. Consider every aspect of routing, and carefully examine each junction before dividing or un-dividing. Regardless of whether you're dividing or un-dividing, remember that you might cause more problems than you solve and you might have to put it back the way it was before. Also remember that dividing and un-dividing each cause loss of some traffic data, which can result in poor Waze routing. ==== {{anchor|How to "Un-Split" two One-Way Roads|How to "Un-divide" two One-Way Roads}}How to un-divide two one-way roads ==== Unfortunately there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before dividing a road in the first place. And then think some more. When you come across a road in your area that has been divided but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way roads UNLESS there are Update Requests related to the road caused by it being divided. {{Red|The process to un-divide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}} The steps below show how to properly merge two one-way roads and preserve the underlying house numbers. This is our example road segment. For the entire length of the road you need to: [[File:undivideRd1.jpg]] 1. Select the two segments to be merged and set them both to two-way. [[File:undivideRd2.jpg]] 2. Disconnect both segments from one side of the section being un-divided. It is best to disconnect alternate ends of each segment as shown. [[File:undivideRd3.jpg]] 3. Bring the two disconnected ends together in the middle (and realign the roads as necessary). You can remove the junction point you just created by selecting it and using the Delete key. [[File:undivideRd4.jpg]] The following video was recorded by an editor merging two one-way roads so the addresses were preserved. This video follows the described steps above, but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen. {{#ev:youtube|6blRMtGwaYA}} After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over. # With the street/road selected, click ‘Edit house numbers’. # From the house number editing view, you need to select each house number one-by-one. # With the house number selected, you see the dashed line is attached to a circle on the street. # Select the circle and move it along the road closest to the entrance of the driveway to the building. Also be sure to check the following: # Remove all "orphaned" junctions. # Change the direction of the preserved segments to two-way. # Check/fix the connectivity of all the roads already connect to the side you kept. # Connect (and set connectivity) of all the roads that used to be connected to the other side. # Make sure all the new two-way segments are connected. # Adjust the geometry to move the two-way road segments to the middle of the road. Now repeat the entire process for the remaining segments matching the two opposite from each other. It isn't difficult once you have gone through the process a couple of times. '''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost. === Highways and Ramps === Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important. ==== Roads ==== The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads almost always should be mapped as separate one-way segments -- and other roads almost never should be. ==== Ramps ==== As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> Remember to check connectivity and turn restrictions while you're there. *There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]]. *Be sure to understand the difference between ramps and [[at-grade connectors]]. ==== Overpasses &amp; Underpasses ==== Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road. Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned. In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment. Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish. ==== Caveat re. Elevation ==== No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information. See also [[Creating and editing road segments#Road elevation|Road Elevation]]. ==== Bridging Roads ==== Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them. Note that Railroad crossings (and other non-navigable types) at grade with a street should not form a junction. See [[Road types/USA#Railroad|Railroads]] under Road Types for more information. ==== Handling Restricted Lanes ==== At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"car pool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road, so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly. The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped. The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separate timed restrictions for each direction on the lanes themselves as well. This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway, makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error. {{details|Carpool, HOV, Transit lanes}} ==== High Occupancy Toll (HOT) Roads/Lanes (USA) ==== The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway. [[Image:I-15-express-lanes.jpg]] HOT roadways have the following features: * These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes. * There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed. * Entrances and exits to the HOT lanes are limited to help maintain high speeds. * There are no entrance/exit combinations where the toll fare rules don't apply. * Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day. HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above. The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute. The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client. Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane. Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation. === Toll roads === :''For other uses see [[Toll (disambiguation)]].'' Roads with tolls can be indicated by checking the '''Toll road''' box on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if: *there is a toll booth, transponder reader, or other tolling device within, or at either end of the segment Do not check the toll box setting for segments that lead up to the final toll segment even if they have no other exit except the final toll segment. In the case of a bridge that is tolled in only one direction, split the road where the toll is collected and mark only the segment with the toll booth as a toll road. * ''see advanced topic on [[Time-based Tolls]] for mapping tolls that do not charge all the time.'' === Time Restricted Turns === {{Time restricted turns}} === When to Use Ramps in an Intersection === Please see the discussion on [[at-grade connectors]]. === When to Create a Roundabout === In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts. '''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]'' === Locking Segments === In some regions there are locking rank standards applied based on road type. In these regions all roads of a certain type are locked to a minimum rank, and should be locked even in residential areas. Check [[Template:Countries|your local wiki]] for your local standards to see if these apply in your editing area. Locking should otherwise be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes. NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct. If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information. '''Locking should be used sparingly and carefully.''' === Junction Style Guide === When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions. == New Roads == === Parking Lots === Mapping a [[Road types/USA#Parking Lot Road|parking lot road]] serves three purposes: *it allows Waze to provide door-to-door directions within the lot; *it allows the Waze client to get off the main road, avoiding erroneous traffic reports. *it prevents the Waze client from routing thru-traffic along the parking lot segments. '''NOTE:''' There are few parking lots that deserve to be designated as a landmark "place". Landmark-worthy parking must be something of a destination in itself, either having a well-known and documented name, or serving multiple unrelated POIs. For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]]. ==== Shopping Centers ==== When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following: *Main entrances from the roads outside the parking lot *Lanes that run along storefronts *Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information) *Primary lanes that serve to get people from one area of the lot to another Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png]] In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map. ==== Small Parking Lots ==== Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area (lots with entrances on both sides) or a single, flattened curve (lots that only have entrances/exits along a single road, such as for strip malls). Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn. ==== Drive-Through Lots ==== Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using three segments]].'' ==== Use of the Parking Lot Road Type ==== The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for navigation vs. the road network. As of June 2012, Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. Every segment that is used to map a parking lot should be of the Parking Lot segment type. It is advised not to mix road types within a parking lot. === Recorded via Client === Once you start editing a road, it changes from red (a new road) to the colour of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users. So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable. Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps. # Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]] # Enter the correct name and road type for your road, following the standards for your country # Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way. # Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one way roads. === Roundabouts === *A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME. *When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map. *Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections. == Classification of crossings == Different types of crossings have [[Classification of crossings|standard ways to handle them]]. {{ReturnToEditingManual}} [[Category:Waze Map Editor]] [[Category:Convert to Subpages]] [[Category:Add Wikilinks]] 1d13f65c505a90a3a6d3f37bf5c3236aab95fc44 10 68 275 274 2015-05-11T14:57:59Z PesachZ 26 Revision notice wikitext text/x-wiki {{mbox|type=construction|text={{red|This page is currently being worked for a '''major revision''' in an off wiki location.}} The content below while mostly accurate may have changed in the interim. The entire page will be rebuilt shortly with fully accurate content pending the completion of new ongoing testing and modification of the TTS engine. Before making any changes to this page, please bring up the issue in the [http://www.waze.com/forum/viewtopic.php?f=129&t=15178 TTS testing forum thread].}} This page covers the abbreviations and acronyms used in naming roads in Waze. Thə list on this page and in the links at the bottom of the page have only been tested for the Engish USA "Samantha" voice. While they should also apply to the English USA "Tom" voice, they have not been tested with any other voice. By following these guidelines the Text-to-speech (TTS) feature will work at its optimum level. If you have questions about these instructions, see the [[Abbreviations_and_acronyms#Further reading|further reading]] at the bottom of this page. ==Standard suffix abbreviations== Waze convention is to use suffix abbreviations in street names. ("Main Rd" instead of "Main Road"). '''Notes:''' # Abbreviate only suffixes. #*"The Avenue", "The Green", etc. should not be abbreviated. #*"Circuit Avenue Road" is abbreviated "Circuit Avenue Rd", not "Cct Ave Rd". #*A road named "Service Road" should not be abbreviated, while "Pipeline Service Road" should be (as "Pipeline Service Rd"). # Suffix abbreviations do ''not'' contain any punctuation, such as "<code>.</code>" (Full-stops) or "<code>-</code>" (Hyphens). # In the event that the original suffix is a plural (ends in s) and only its singular form is present as an abbreviation, simply adding an "s" to the end of the abbreviation may or may not work as expected unless specified below. # When 'N', 'S', 'E', or 'W' should NOT be pronounced as compass directions, enclose the letter in single quotes. #* George 'W' Bush Blvd #* West 'W' Lee Ave # If your question is not answered here, please ask in the [//www.waze.com/forum/viewtopic.php?f=129&t=15178 TTS testing topic on the waze forums] # As of 2015-03-18, some entries in this table are no longer valid. They will be updated when resources are available. Legend: * TTS = Text To Speech for supported countries. {| class="wikitable sortable" style="background:white; font-size:80%; margin: 1em auto 1em auto" border="1" | align="center" style="background:#f0f0f0;"|'''Road Name ''' | align="center" style="background:#f0f0f0;"|''' Abbreviation ''' | align="center" style="background:#f0f0f0;"|''' TTS Compatibility ''' |- | Alley|| Aly || Yes |- | Annex|| Anx|| Yes |- | Arcade|| Arc|| Yes |- | Avenue|| Ave|| Yes |- | Bayoo|| Byu|| Yes |- | Beach|| Bch|| Yes |- | Bend|| Bnd|| Yes |- | Bluff|| Blf|| Yes |- | Bottom|| Btm|| Yes |- | Boulevard|| Blvd|| Yes |- | Branch|| Br|| Yes |- | Bridge|| Brg|| Yes |- | Broadway|| Bdwy|| Untested |- | Brook|| Brk|| Yes |- | Brooks||Brks|| Yes |- | Burg||Bg|| Incompatible |- | Burgs||Bgs|| Untested |- | Bypass||Byp|| Yes |- | Camp||Cp|| Yes |- | Canyon||Cyn|| Yes |- | Cape||Cpe|| Untested |- | Causeway||Cswy|| Yes |- | Center||Ctr|| Yes |- | Centers||Ctrs|| Untested |- | Circle||Cir|| Yes |- | Circles||Cirs|| Untested |- | Circuit||Cct|| Untested |- | Cliff||Clf|| Untested |- | Cliffs||Clfs|| Untested |- | Close|| Cl|| Yes |- | Club||Clb|| Yes |- | Common||Cmn|| Yes |- |Commons||Cmns|| Yes |- | Corner||Cor|| Untested |- | Corners||Cors|| Untested |- | Course||Crse|| Yes |- | Court|| Ct|| Yes |- | Courts||Cts|| Untested |- | Cove||Cv|| Incompatible |- | Coves||Cvs|| Untested |- | Creek||Crk|| Untested |- | Crescent||Cres|| Yes |- | Crest||Crst|| Yes |- | Crossing||Xing|| Yes |- | Crossroad||Xrd|| Yes |- | Curve||Curv|| Yes |- | Dale||Dl|| Yes |- | Dam||Dam|| Yes |- | Divide||Dv|| Incompatible |- | Drive|| Dr|| Yes |- | Drives||Drs|| Untested |- | Estate||Est|| Untested |- | Estates||Ests|| Untested |- | Expressway||Expy|| Yes |- | Extension||Ext|| Yes |- | Extensions||Exts|| Untested |- | Fall||Fall|| Untested |- | Falls||Fls|| Yes |- | Ferry||Fry|| Untested |- | Field||Fld|| Untested |- | Fields||Flds|| Untested |- | Flat||Flt|| Yes |- | Flats||Flts|| Untested |- | Ford||Frd|| Untested |- | Fords||Frds|| Untested |- | Forest||Frst|| Untested |- | Forge||Frg|| Untested |- | Forges||Frgs|| Untested |- | Fork||Frk|| Untested |- | Forks||Frks|| Untested |- | Fort||Ft|| Yes |- | Freeway|| Fwy|| Yes |- | Garden|| Gdn|| Yes |- | Gardens|| Gdns|| Yes |- | Gateway||Gtwy|| Yes |- | Glen||Gln|| Yes |- | Glens||Glns|| Untested |- | Green||Grn|| Yes |- | Greens||Grns|| Untested |- | Grove|| Grv|| Yes |- | Groves||Grvs|| Untested |- | Harbor||Hbr|| Yes |- | Harbors||Hbrs|| Untested |- | Haven||Hvn|| Untested |- | Heights||Hts|| Yes |- | Highway|| Hwy|| Yes |- | Hill||Hl|| Yes |- | Hills||Hls|| Yes |- | Hollow||Holw|| Yes |- | Inlet||Inlt|| Yes |- | Island||Is|| Untested |- | Islands||Iss|| Untested |- | Isle||Il|| Yes |- | Junction||Jctn|| Yes |- | Junctions||Jctns|| Yes |- | Key||Key|| Yes |- | Keys||Keys|| Yes |- | Knoll||Knl|| Yes |- | Knolls||Knls|| Yes |- | Lake||Lk|| Untested |- | Lakes||Lks|| Untested |- | Land||Land|| Untested |- | Landing||Lndg|| Yes |- | Lane|| Ln|| Yes |- | Light||Lgt|| Yes |- | Lights||Lgts|| Yes |- | Loaf||Lf|| Yes |- | Lock||Lck|| Yes |- | Locks||Lcks|| Yes |- | Lodge||Ldg|| Yes |- | Loop||Loop|| Yes |- | Mall||Mall|| Yes |- | Manor||Mnr|| Yes |- | Manors||Mnrs|| Yes |- | Meadow||Mdw|| Yes |- | Meadows||Mdws|| Yes |- | Mews||Mews|| Yes |- | Mill||Ml|| Untested |- | Mills||Mls|| Untested |- | Mission||Msn|| Yes |- | Motorway||Mtwy|| Yes |- | Mount|| Mt|| Yes |- | Mountain||Mtn|| Yes |- | Mountains||Mtns|| Yes |- | Neck||Nck|| Yes |- | Orchard||Orch|| Yes |- | Oval||Oval|| Yes |- | Overpass||Opas|| Yes |- | Parade|| Pde|| Yes |- | Park|| Pk|| Yes |- | Parks||Pks|| Yes |- | Parkway||Pkwy|| Yes |- | Parkways||Pkwys|| Yes |- | Pass||Pass|| Yes |- | Passage||Psge|| Yes |- | Path||Path|| Yes |- | Pike||Pke|| Yes |- | Pine||Pne|| Yes |- | Pines||Pnes|| Yes |- | Place|| Pl|| Yes |- | Plain||Pln|| Untested |- | Plains||Plns|| Yes |- | Plaza||Plz|| Yes |- | Point||Pt|| Incompatible |- | Points||Pts|| Yes |- | Port||Prt|| Yes |- | Ports||Prts|| Yes |- | Prairie||Prr|| Yes |- | Radial||Radl|| Yes |- | Ramp||Ramp|| Yes |- | Ranch||Rnch|| Yes |- | Rapid||Rpd|| Incompatible |- | Rapids||Rpds|| Yes |- | Rest||Rst|| Untested |- | Ridge||Rdge|| Yes |- | Ridges||Rdgs|| Untested |- | Rise||Rise|| Untested |- | River||Riv|| Yes |- | Road|| Rd|| Yes |- | Roads||Rds|| Untested |- | Route||Rte|| Yes |- | Row||Row|| Yes |- | Rue||Rue|| Yes |- | Run||Run|| Yes |- | Saint||St.||Yes |- | Shoal||Shl|| Yes |- | Shoals||Shls|| Yes |- | Shore||Shr|| Yes |- | Shores||Shrs|| Yes |- | Skyway||Skwy|| Yes |- | Spring||Spg|| Yes |- | Springs||Spgs|| Yes |- | Spur||Spur|| Untested |- | Square|| Sq|| Yes |- | Squares||Sqs|| Yes |- | Station||Sta|| Yes |- | Stream||Strm|| Yes |- | Street|| St|| Yes |- | Streets||Sts|| Yes |- | Summit||Smt|| Yes |- | Terrace|| Ter|| Yes |- | Terrace|| Tce|| Yes |- | Throughwawy||Thwy|| Yes |- | Trace||Trce|| Yes |- | Track||Trak|| Yes |- | Trafficway||Trfy|| Yes |- | Trail||Trl|| Yes |- | Tunnel||Tunl|| Yes |- | Turnpike||Tpk|| Yes |- | Underpass||Upas|| Yes |- | Union||Un|| Untested |- | Unions||Uns|| Yes |- | Upper||Uppr||Yes |- | Valley||Vly|| Yes |- | Valleys||Vlys|| Yes |- | Viaduct||Vdct|| Yes |- | View||Vw|| Yes |- | Views||Vws|| Yes |- | Village||Vlg|| Yes |- | Villages||Vlgs|| Yes |- | Ville||Vl|| Untested |- | Vista||Vis|| Yes |- | Walk||Walk|| Yes |- | Wall||Wall|| Yes |- | Waters||Wtr|| Untested |- | Way||Way|| Yes |- | Ways||Ways|| Yes |- | Well||Wl|| Yes |- | Wells||Wls|| Yes |} ==Further reading== UK editors should see [[How to classify and name roads (United_Kingdom)#Abbreviations|How to classify and name roads (United_Kingdom)]] for UK specific abbreviations, some of which differ. Canadian editors should see [[Canada#Abbreviations]] for Canada-specific abbreviations, some of which differ. Other countries may have differing guidance; refer to the country-specific pages for any local guidance. === Forums === If you have further questions on this topic, please refer to the following Waze forum for a "Work in progress" list of abbreviations that are being tested, currently available, and proposed: [http://www.waze.com/forum/viewtopic.php?f=10&t=15178 Test of Text-to-Speech (TTS) Abbreviations in Waze Clients] === Glossary === Refer to the [[Glossary]] page for definitions of many terms used in Waze. c4afb4a9e57851c7fab3977aba3eb7aa7fe7505d 0 13 10788 10787 2015-05-21T10:09:01Z BellHouse 29 /* Anmeldung Area-Manager */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Den Editoren seiner Gegend Hilfestellung leisten. * Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. == Anmeldung Area-Manager == Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Schon recht sattelfest in den Editier-Regeln sein *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:''' *Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. *Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. *Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. *Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. *Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. *Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". *Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. *Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *Caradellino (AT) *argus-cronos (CH) *svx-biker (CH) *pikifoo (CH) === Richtlinien, die Du genau kennen solltest! === '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. === Online-Formular === Folgendes musst Du tun: *Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. *Klicke auf [[WME Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. *Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. *Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt bald) * Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 5d756c4c4166e7dd5572d866eb905e642f7e2a86 10789 10788 2015-12-11T13:22:59Z Vince1612 23 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Den Editoren seiner Gegend Hilfestellung leisten. * Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. == Anmeldung Area-Manager == Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Schon recht sattelfest in den Editier-Regeln sein *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:''' *Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. *Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. *Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. *Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. *Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. *Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". *Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. *Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *Caradellino (AT) *popel22 (CH) *svx-biker (CH) *pjw65 (CH) === Richtlinien, die Du genau kennen solltest! === '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. === Online-Formular === Folgendes musst Du tun: *Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. *Klicke auf [[WME Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. *Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. *Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt bald) * Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 1d1464856f761a1a5b16a754d8243f517420eeb6 0 1 1 2015-06-21T08:15:04Z MediaWiki default 0 wikitext text/x-wiki <strong>MediaWiki has been successfully installed.</strong> Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list] * [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] * [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language] 8e0aa2f2a7829587801db67d0424d9b447e09867 10141 10140 2016-01-17T20:40:30Z Popel22 24 Rollen / Funktionen aus dem DE wiki kopiert wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Guide de l'édition en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sites in english</p> <div style="padding:5px"> * [[How to label and name roads (Switzerland)]] * [[How to label and name roads|More countries]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 06f010f334cad5b3409e686ab9087cb28d4f676a 10 35 11439 11438 2015-07-05T03:46:23Z PesachZ 26 Add anchor for compatibility with section link generated after editing a page a/p [https://www.waze.com/forum/viewtopic.php?p=1149178#p1149178 forum] wikitext text/x-wiki <includeonly><span id="{{{1|}}}">{{{1|}}}</span> {{anchor|.7B.7B.40.7C{{{1|}}}.7D.7D}}[[File:Link.png|12px|text-top|link={{FULLPAGENAME}}#{{#if:{{{2|}}}|{{{2}}}|{{{1|}}}}}|link to this section]]</includeonly><noinclude> {{documentation}} </noinclude> 783d70f3ce9b50a2bcdc9d39e95e3ae8c110446c 11452 11451 2016-03-10T06:17:41Z PesachZ 26 added anchor for {{{2}}} wikitext text/x-wiki <includeonly><span id="{{{1|}}}">{{{1|}}}</span> {{anchor|.7B.7B.40.7C{{{1|}}}.7D.7D|{{{2|}}}}}[[File:Link.png|12px|text-top|link={{FULLPAGENAME}}#{{#if:{{{2|}}}|{{{2}}}|{{{1|}}}}}|link to this section]]{{#if:{{{edit|}}}|{{nbsp}}<div class="mw-editsection plainlinks">[[File:Edit.png|15px|baseline|link={{fullurl:{{{edit}}}|action=edit}}|edit]]</div>}}</includeonly><noinclude> {{documentation}} </noinclude> 6bc08d9ca26fe4fc2e61993e2110cdbf02d2e2e8 10 42 11492 11491 2015-10-07T07:28:12Z Kentsmith9 25 testing margin wikitext text/x-wiki <includeonly><div class="toccolours mw-collapsible {{#ifeq:{{{expand}}}|yes||mw-collapsed}}" style="width:100%; border: hidden; background-color: transparent; margin: 20px"></includeonly><noinclude>{{Documentation}}</noinclude> 13aab8df2fc48cceca355584c972f1da1555fed3 11493 11492 2015-10-07T07:29:19Z Kentsmith9 25 Removed test wikitext text/x-wiki <includeonly><div class="toccolours mw-collapsible {{#ifeq:{{{expand}}}|yes||mw-collapsed}}" style="width:100%; border: hidden; background-color: transparent"></includeonly><noinclude>{{Documentation}}</noinclude> b09b9d14b1eaf3560f7c9c6074e8b20194dc9821 11494 11493 2015-10-25T14:44:56Z PesachZ 26 Added a manual style override wikitext text/x-wiki <includeonly><div class="toccolours mw-collapsible {{#ifeq:{{{expand}}}|yes||mw-collapsed}}" style="width:100%; border: hidden; background-color: transparent {{#if:{{{style|}}}|;{{{style}}}}}"></includeonly><noinclude>{{Documentation}}</noinclude> ce497271d80044641f2e9123325c1b4a4c48d834 10 65 11780 2015-10-22T16:06:44Z PesachZ 26 Created page with "<div style="-webkit-column-count: {{{1|2}}}; /* Chrome, Safari, Opera */ -moz-column-count: {{{1|2}}}; /* Firefox */ column-count: {{{1|2}}};">{{{2|{{red|Error: You mu..." wikitext text/x-wiki <div style="-webkit-column-count: {{{1|2}}}; /* Chrome, Safari, Opera */ -moz-column-count: {{{1|2}}}; /* Firefox */ column-count: {{{1|2}}};">{{{2|{{red|Error: You must put the content of the columns as the second unnamed parameter}}}}}</div><noinclude>{{doc}} c8b6f5356d917505144848a7253e535cf3a7e292 11781 11780 2015-10-22T16:09:25Z PesachZ 26 wikitext text/x-wiki <includeonly><div style="-webkit-column-count: {{{1|2}}}; /* Chrome, Safari, Opera */ -moz-column-count: {{{1|2}}}; /* Firefox */ column-count: {{{1|2}}};">{{{2|{{red|Error: You must put the content of the columns as the second unnamed parameter}}}}}</div></includeonly><noinclude>{{doc}}</noinclude> 0e085c43052661185e88bc72470965cffb000046 11782 11781 2015-10-22T16:12:40Z PesachZ 26 wikitext text/x-wiki <includeonly><div style="-webkit-column-count: {{{2|2}}}; /* Chrome, Safari, Opera */ -moz-column-count: {{{2|2}}}; /* Firefox */ column-count: {{{2|2}}};">{{{1|{{red|Error: You must put the content of the columns as the second unnamed parameter}}}}}</div></includeonly><noinclude>{{doc}}</noinclude> c7b859ab224dba497a97d4f55dd67d8251425bd3 10 28 11375 11374 2015-11-28T19:19:06Z Kentsmith9 25 Fixed Swiss flag formatting with 25x15 variation with transparency to support 15x15 flag wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:CountriesList&action=edit --> <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> *[[Image:Sq.png]]&nbsp;[[Albania|Albania (Shqipëria)]] *[[Image:Ar.png]]&nbsp;[[Argentina]] *[[Image:Au.png]]&nbsp;[[Australia]] *[[Image:Oesterreich.png]]&nbsp;[[Österreich|Austria (Österreich)]] *[[Image:Be.png]]&nbsp;[[Belgium]] *[[Image:Br.png]]&nbsp;[[Brasil]] *[[Image:Bg.png]]&nbsp;[[България|Bulgaria (България)]] *[[Image:Ca.png]]&nbsp;[[Canada]] *[[Image:Cl.png]]&nbsp;[[Chile]] *[[Image:Cn.png]]&nbsp;[[中国|China (中国)]] *[[Image:Co.png]]&nbsp;[[Colombia]] *[[Image:Cr.png]]&nbsp;[[Costa Rica]] *[[Image:Cy.png]]&nbsp;[[Cyprus]] *[[Image:Cz.png]]&nbsp;[[Czech]] *[[Image:Dk.png]]&nbsp;[[Denmark]] *[[Image:Ee.png]]&nbsp;[[Eesti|Estonia (Eesti)]] *[[Image:Fi.jpg]]&nbsp;[[Finland]] *[[Image:Fr.png]]&nbsp;[[France]] *[[Image:De.png]]&nbsp;[[Deutschland|Germany]] *[[Image:Hu.png]]&nbsp;[[Hungary|Hungary]] *[[Image:Ic.png]]&nbsp;[[Iceland]] *[[Image:India1.jpg]]&nbsp;[[India]] *[[Image:In.png]]&nbsp;[[Indonesia]] *[[Image:Ie.png]]&nbsp;[[Ireland]] *[[Image:Il.png]]&nbsp;[http://www.waze.com/he/wiki/index.php?title=%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 Israel(ישראל)] *[[Image:It.png]]&nbsp;[[Italy]] *[[Image:Japan-flag.jpg||25px]]&nbsp;[[日本|Japan (日本)]] *[[Image:Korea-flag.png||25px]]&nbsp;[[Korea|Korea (대한민국)]] *[[Image:Kv.png]]&nbsp;[[Kosovo]] *[[Image:Lv.png]]&nbsp;[[Latvija|Latvia]] *[[Image:Lithuania_flag.png|25px]]&nbsp;[[Lietuviškai|Lietuva]] *[[Image:Lux.gif]]&nbsp;[[Luxembourg|Luxembourg]] *[[Image:My.jpg]]&nbsp;[[Malaysia]] *[[Image:Mexico.png]]&nbsp;[[México]] *[[Image:Na.png|25px]]&nbsp;[[Namibia]] *[[Image:Nl.png]]&nbsp;[[Nederland]] *[[Image:Nz.png]]&nbsp;[[New Zealand|New&nbsp;Zealand]] *[[Image:Ni.png]]&nbsp;[[Nicaragua]] *[[Image:Norway_flag.png]]&nbsp;[[Norway]] *[[Image:Pl.png]]&nbsp;[[Poland]] *[[Image:Pt.png]]&nbsp;[[Portugal]] *[[Image:Ro.png]]&nbsp;[[Romania]] *[[Image:Ru.png]]&nbsp;[[Russia]] *[[Image:SRb.png]]&nbsp;[[Serbia]] *[[Image:Sk.png]]&nbsp;[[Slovakia]] *[[Image:SI.png]]&nbsp;[[Slovenia]] *[[Image:Za.png]]&nbsp;[[South Africa|South&nbsp;Africa]] *[[Image:Sr.png]]&nbsp;[[Suriname]] *[[Image:Es.png]]&nbsp;[[España|Spain (España)]] *[[Image:Se.png]]&nbsp;[[Sweden]] *[[Image:Swiss1.gif]]&nbsp;[[Switzerland]] *[[Image:Th.png]]&nbsp;[[Thailand]] *[[Image:Turkey.png]]&nbsp;[[Türkiye|Turkey (Türkiye)]] *[[Image:Ua.jpg]]&nbsp;[[Ukraine]] *[[Image:Gb.png]]&nbsp;[[United Kingdom|United&nbsp;Kingdom]] *[[Image:Us.png]]&nbsp;[[USA]] </div> ----<!-- --><noinclude>[[Category:Country list]]</noinclude> d4bcc41e58eaf31ab4844129b95bd02c14a7c71c 11380 11379 2016-04-28T02:02:29Z PesachZ 26 Made this page pull from. {{Countries}} to prevent the necessity of duplicate edits and reduce errors. Also switched to using {{columns}} wikitext text/x-wiki <noinclude>{{mbox|type=wiki|text=Please do not edit this page, any countries should be added to the {{Tl|Countries}} template page, and will be populated here.}}</noinclude> {{Columns|{{CountriesList}}|3}} ----<!-- --><noinclude>[[Category:Country list]]</noinclude> a3d930018bc86174ec85f083791a461383578625 10 66 11863 11862 2015-11-28T19:21:36Z Kentsmith9 25 Replaced Swiss flag with 25x15 using transparency to support true 15x15 flag format wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Oesterreich.png]] [[Österreich|Austria (Österreich)]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|Bulgaria (България)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|China (中国)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:De.png]] [[Deutschland|Germany (Deutschland)]] <li>[[Image:Gr.png]] [[Greece|Greece (Ελλάδα)]] <li>[[Image:Hu.png]] [[Hungary|Hungary (Magyarország)]] <li>[[Image:Ic.png]] [[Iceland]] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:It.png]] [[Italy]] <li>[[image:Japan-flag.jpg||25px]] [[日本|Japan (日本)]] <li>[[Image:Kr.png|25px]] [[Korea|Korea (대한민국)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:Lv.png]] [[Latvija|Latvia (Latviešu)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuva (Lietuviškai)]] <li>[[Image:Lux.gif]] [[Luxembourg|Luxembourg (Lëtzebuerg)]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Ni.png]] [[Nicaragua]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Es.png]] [[España|Spain (España)]] <li>[[Image:Sr.png]] [[Suriname]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.gif]] [[Switzerland]] <li>[[Image:Th.png]] [[Thailand]] <li>[[Image:Turkey.png]] [[Türkiye|Turkey (Türkiye)]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 6783e2e899a8d2b475321f55f4300ff114367db7 11865 11864 2016-03-15T09:12:23Z WonderLerm 22 wikitext text/x-wiki <!-- When you update this list, please also update http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0" class="CountriesList"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Oesterreich.png]] [[Österreich|Austria (Österreich)]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|Bulgaria (България)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|China (中国)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:De.png]] [[Deutschland|Germany (Deutschland)]] <li>[[Image:Gr.png]] [[Greece|Greece (Ελλάδα)]] <li>[[Image:Hu.png]] [[Hungary|Hungary (Magyarország)]] <li>[[Image:Ic.png]] [[Iceland]] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:It.png]] [[Italy]] <li>[[image:Japan-flag.jpg||25px]] [[日本|Japan (日本)]] <li>[[Image:Kr.png|25px]] [[Korea|Korea (대한민국)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:Lv.png]] [[Latvija|Latvia (Latviešu)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuva (Lietuviškai)]] <li>[[Image:Lux.gif]] [[Luxembourg|Luxembourg (Lëtzebuerg)]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Ni.png]] [[Nicaragua]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:PE.png]] [[Perú]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Es.png]] [[España|Spain (España)]] <li>[[Image:Sr.png]] [[Suriname]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.gif]] [[Switzerland]] <li>[[Image:Th.png]] [[Thailand]] <li>[[Image:Turkey.png]] [[Türkiye|Turkey (Türkiye)]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> d5dfdc631703c8fac42e70f4afbb10a8eff4ec64 11869 11868 2016-04-28T06:12:52Z PesachZ 26 comment on top, and refreshing for flag images SG and VN wikitext text/x-wiki <!-- When you update this list, please also purge if needed http://www.waze.com/wiki/index.php?title=Template:Countries&action=Edit --> <ul style="list-style:none;margin:0" class="CountriesList"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Oesterreich.png]] [[Österreich|Austria (Österreich)]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Bh.png]] [[BiH|Bosnia and Herzegovina]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|Bulgaria (България)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|China (中国)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:De.png]] [[Deutschland|Germany (Deutschland)]] <li>[[Image:Gr.png]] [[Greece|Greece (Ελλάδα)]] <li>[[Image:Hu.png]] [[Hungary|Hungary (Magyarország)]] <li>[[Image:Ic.png]] [[Iceland]] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:It.png]] [[Italy]] <li>[[image:Japan-flag.jpg||25px]] [[日本|Japan (日本)]] <li>[[Image:Kr.png|25px]] [[Korea|Korea (대한민국)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:Lv.png]] [[Latvija|Latvia (Latviešu)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuva (Lietuviškai)]] <li>[[Image:Lux.gif]] [[Luxembourg|Luxembourg (Lëtzebuerg)]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Ni.png]] [[Nicaragua]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:PE.png]] [[Perú]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sg.png]] [[Singapore]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Es.png]] [[España|Spain (España)]] <li>[[Image:Sr.png]] [[Suriname]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.gif]] [[Switzerland]] <li>[[Image:Th.png]] [[Thailand]] <li>[[Image:Turkey.png]] [[Türkiye|Turkey (Türkiye)]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] <li>[[Image:Vn.png]] [[Vietnam]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 0ba75781d390324631bc393cfca729219105f1e0 0 7 10475 10474 2016-01-17T20:59:16Z Popel22 24 "Fusswegartikel" von DE kopiert wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen * <span style="color:RoyalBlue;">'''Zufahrtsstraße'''</span> => werden nicht verwendet! ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' '''Da Waze eine reine Autofahrer-App ist, sind Strecken dieser Typen in der Regeln nicht anzulegen. Weitere Hinweise dazu: [[Fußwege_und_Privatstraßen|Fußwege und Privatstraßen]]'''''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. Lies das Thema [[Fußwege und Privatstraßen]]. =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. * Ausfahrt Zürich Flughafen, Ausfahrt Bülach-Nord * Einfahrt > Basel Bern Luzern, Einfahrt > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Einfahrt > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Sie dürfen keine Verbindung zu existierenden Strassen haben und sollen mit Level -5 versehen werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 5 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 5ca3196a969b6c8d4142fd04d88b50d1eed454f0 10476 10475 2016-01-17T21:00:36Z Popel22 24 wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen * <span style="color:RoyalBlue;">'''Zufahrtsstraße'''</span> => werden nicht verwendet! ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. Lies das Thema [[Fußwege und Privatstraßen]]. =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. * Ausfahrt Zürich Flughafen, Ausfahrt Bülach-Nord * Einfahrt > Basel Bern Luzern, Einfahrt > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Einfahrt > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Sie dürfen keine Verbindung zu existierenden Strassen haben und sollen mit Level -5 versehen werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 5 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] c247170144484ad4ccfbdd6bb20c4adac1002653 10477 10476 2016-01-17T21:01:19Z Popel22 24 wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen * <span style="color:RoyalBlue;">'''Zufahrtsstraße'''</span> => werden nicht verwendet! ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. * Ausfahrt Zürich Flughafen, Ausfahrt Bülach-Nord * Einfahrt > Basel Bern Luzern, Einfahrt > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Einfahrt > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Sie dürfen keine Verbindung zu existierenden Strassen haben und sollen mit Level -5 versehen werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 5 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 134947e638090184a8834389fbd76e9dcd38cf0c 10 66 11870 11869 2016-04-28T06:16:08Z PesachZ 26 turn edit nor into clickable purge link in <noinclude> box wikitext text/x-wiki <noinclude>{{mbox|type=wiki|text=When you update this list, please also purge {{tl|Countries}} by [http://wiki.waze.com/wiki/index.php?action=purge&forcelinkupdate&title=Template:Countries clicking here].}}</noinclude> <ul style="list-style:none;margin:0" class="CountriesList"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Oesterreich.png]] [[Österreich|Austria (Österreich)]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Bh.png]] [[BiH|Bosnia and Herzegovina]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|Bulgaria (България)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|China (中国)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:De.png]] [[Deutschland|Germany (Deutschland)]] <li>[[Image:Gr.png]] [[Greece|Greece (Ελλάδα)]] <li>[[Image:Hu.png]] [[Hungary|Hungary (Magyarország)]] <li>[[Image:Ic.png]] [[Iceland]] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:It.png]] [[Italy]] <li>[[image:Japan-flag.jpg||25px]] [[日本|Japan (日本)]] <li>[[Image:Kr.png|25px]] [[Korea|Korea (대한민국)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:Lv.png]] [[Latvija|Latvia (Latviešu)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuva (Lietuviškai)]] <li>[[Image:Lux.gif]] [[Luxembourg|Luxembourg (Lëtzebuerg)]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Ni.png]] [[Nicaragua]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:PE.png]] [[Perú]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sg.png]] [[Singapore]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Es.png]] [[España|Spain (España)]] <li>[[Image:Sr.png]] [[Suriname]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.gif]] [[Switzerland]] <li>[[Image:Th.png]] [[Thailand]] <li>[[Image:Turkey.png]] [[Türkiye|Turkey (Türkiye)]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] <li>[[Image:Vn.png]] [[Vietnam]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> 5d1cd90acb7ee695c823ea5daf939aaac20e2e35 10 28 11381 11380 2016-04-28T06:16:33Z PesachZ 26 typo wikitext text/x-wiki <noinclude>{{mbox|type=wiki|text=Please do not edit this page, any countries should be added to the {{Tl|CountriesList}} template page, and will be populated here.}}</noinclude> {{Columns|{{CountriesList}}|3}} ----<!-- --><noinclude>[[Category:Country list]]</noinclude> edec4fea3899d8ec2cfd4b47433e90947d6574e9 11382 11381 2016-06-19T20:38:07Z Wottem 21 109 Versionen importiert wikitext text/x-wiki <noinclude>{{mbox|type=wiki|text=Please do not edit this page, any countries should be added to the {{Tl|CountriesList}} template page, and will be populated here.}}</noinclude> {{Columns|{{CountriesList}}|3}} ----<!-- --><noinclude>[[Category:Country list]]</noinclude> edec4fea3899d8ec2cfd4b47433e90947d6574e9 10 58 11747 11746 2016-04-28T06:21:03Z PesachZ 26 add wiki as a supported type wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox warning yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | neweditor = Mbox new editor.png | mail = Mbox mail.png | forum = Gnome-system-users.svg.png | cleanup = Edit-clear.png | wiki = wikitext.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> {{Documentation|content=This subtemplate supports the default values of {{tl|Mbox}}. It should not be altered without review from a Wiki Expert. Contact one through the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion forum.]}} <!-- This category is only for the template itself --> [[Category:Template:Mbox]] </noinclude> b82054418fd6c64d000e0b5b5e581d9a5f09f3a3 0 12 10745 10744 2016-05-17T13:12:16Z Vince1612 23 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} c38c2247ce0d488cedd29fbbf169e8e448bc62be 10746 10745 2016-05-18T18:55:08Z Vince1612 23 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} b0ae2fd699e3c967bd41c1e815286023405a052b 10748 10747 2016-06-19T20:35:13Z Wottem 21 46 Versionen importiert wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1 (inaktiv)||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} b133fda972f350dcc339117706f5142006d69f9e 0 1 10142 10141 2016-06-19T20:33:13Z Wottem 21 97 Versionen importiert wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Guide de l'édition en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sites in english</p> <div style="padding:5px"> * [[How to label and name roads (Switzerland)]] * [[How to label and name roads|More countries]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 06f010f334cad5b3409e686ab9087cb28d4f676a 0 2 10161 10160 2016-06-19T20:33:14Z Wottem 21 18 Versionen importiert wikitext text/x-wiki * [[Diskussionsforum]] * [[Die Waze Pendler Gruppen]] * [[Der Waze Chat]] * [[Straßen Berichte]] * [[Facebook Verbindung]] [[Facebook]] * [http://www.waze.com/blog/ Waze Blog] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 6c4fe1345adaca5de7ee48a8a022c21907250c51 0 3 10207 10206 2016-06-19T20:33:31Z Wottem 21 45 Versionen importiert wikitext text/x-wiki == '''Version 3+''' == [[Anleitung zum Bearbeiten der Karte|Zurück zu Anleitung zum Bearbeiten der Karte]] [[Image:Wiki_35_header.png|540px| center]] <div style="text-align: left;"> *[[Waze installieren]] <br/> *[[Mit Waze verbinden]] <br/> *[[Navigieren]] <br/> *[[Meldungen erstellen]] <br/> *[[Favoriten verwalten]] <br/> *[[Tankstellen]] <br/> *[[Waze Symbole]] <br/> *[[Sprachbefehle]] <br/> *[[Wie sehe ich meine Freunde unterwegs]] <br/> *[[Meine Facebook Freunde bei Waze]] <br/> *[[Facebook und Privatsphäre]] <br/> *[[Einchecken mit Facebook]] <br/> *[[Abholen mit Waze]] <br/> *[[Fahrten teilen]] <br/> *[[Zielannäherung]] <br/> *[[Unsichtbar]] <br/> *[[Private Mitteilungen]] <br/> *[[Fahrziel und Standort teilen]] <br/> *[[Tipps und Tricks]] <br/> </div> [[Category:Version 3.5]] [[Category:Anleitung]] ff5f73932ea905585abf8d2c737c5deb5f5d114d 0 4 10249 10248 2016-06-19T20:33:34Z Wottem 21 41 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Karte von Waze ist besonders aktuell. Kartenbearbeitung ist jederzeit im Waze Map Editor (WME) möglich, und in kurzen Abständen wird der aktuelle Stand von Waze in das Navigationssystem übernommen. Waze strebt an, diese Aktualisierung täglich durchzuführen. Dabei wird der Kartenstand zu einem bestimmten Zeitpunkt kopiert, für die Navigation umgerechnet und dann auf den Routingserver übertragen. Dieser Ablauf dauert etwas weniger als einen Tag. Durch den einmal täglich startenden Verarbeitungslauf und die etwa einen Tag dauernde Verarbeitung sind bei optimalem Betrieb die Kartenänderungen am übernächsten Tag auf dem Routingserver angekommen. * Informiere dich hier: [http://status.waze.com Die offizielle Waze Status Seite] bevor Du reklamierst. ==Karten-Aktualisierung== Wenn die App gestartet wird und eine Route berechnet, werden die für die Anzeige nötigen Kartenteile (Kacheln, ca 1kmx1km groß) vom Server geladen. Die App lädt dabei immer die nächsten Streckenabschnitte im Voraus, um auch bei kurzen Funklöchern noch einwandfrei zu funktionieren. Um Datenübertragung zu sparen, werden die Kartendaten einige Tage in der App zwischengespeichert (gecachet). Deshalb können nach dem App-Start ohne Navigation auch gelegentlich Kartendaten angezeigt werden die schon einige Tage alt sind. Wenn man mit laufender Routennavigation fährt ist sichergestellt, dass alle Kartendaten entlang der Strecke aktuell sind. ==Verkehrsmeldungen== Verkehrsmeldungen werden in Echtzeit an die Waze-App auf deinem Smartphone gesendet. Dazu gehören Geschwindigkeiten des Verkehrs und Unfallberichte. Die App lädt diese Daten während der Fahrt im Abstand von wenigen Minuten vom Server. ==Aktualisierungsanfragen (Update Requests)== Aktualisierungsanfragen erscheinen im Karteneditor in Echtzeit. ==Die Karte bearbeiten mit WME== Wenn Du nicht [[Der Area Manager|Area Manager]] bist, kannst du nur innerhalb einer Meile oder innerhalb von 1.6 Kilometern um die befahrenen Straßen herum die Karte mit dem Karteneditor(WME) bearbeiten. Die Rechte, um im besagten Radius zu arbeiten sind nicht sofort vorhanden. Normalerweise sind diese spätestens 2 Tage nach dem Erscheinen der gefahrenen Strecken im [[Mein Dashboard|Dashboard]] vorhanden. ==Deine Routen== Wenn Du mit Waze herum fährst, werden deine gefahrenen Strecken im [[Mein Dashboard|Dashboard]] gespeichert. Das letzte Aktualisierungsdatum der Routen steht unten. Im Karteneditor sind die Daten im Reiter "Fahrten" mit Datum/Zeit und Länge/Zeit der gefahrenen Strecke abrufbar. In der Regel sind die gefahrenen Strecken - seit der neue Merger Prozess initialisiert wurde - innerhalb weniger Stunden im Dashboard und Reiter "Fahrten" des Karteneditors ersichtlich. Falls dem nicht so ist, gibt es wichtigere Probleme, die Waze zu der Zeit lösen muss. ==Neu aufgezeichnete Straßen== Wenn Du [[Zeichne Straße auf|neue Straßen aufzeichnest]] werden sie als rote Linien in der App angezeigt, Im [[Der Waze Map-Editor|Karteneditor]] sind diese erst zu sehen, wenn sie auch im [[Mein Dashboard|Dashboard]] resp. im Reiter "Fahrten" des Karteneditors zu sehen sind. Wenn die Straße im [[Der Waze Map-Editor|Karteneditor]] bearbeitet wurde und ein Karten-Update von Waze gemacht wurde, erscheint sie auch in der App und in der [https://www.waze.com/de/livemap/ Live Map]. Die Frist bis diese Straße erscheint liegt bei 2-5 Tagen. Wenn Waze Probleme (Server, Software..) hat, kann es um Einiges länger dauern (bis zu 2-3 Wochen). Wenn die Live-Map aktualisiert wurde, kann es noch einen Tag dauern bis der Routing-Server Deine Straße korrekt behandelt. Du kannst diese Straße in der App sehen und als Ziel annavigieren, aber als Standort in der Suche erscheint sie nicht. In diesem Fall, ist das Routing schlecht oder schlägt fehl. Nun, auch wenn wir manchmal lange warten müssen, die Aktualisierung ist vielfach schneller als bei den meisten anderen GPS-basierten Anwendungen. ==Punkte== Allgemein: Punkte erscheinen nie unmittelbar nachdem man sie erhalten hat in der Statistik. Wenn die [[client device|Anwendung]] sich mit Waze verbindet, erhält sie die angezeigten Punkte von der Waze Statistik. Da Du mit Fahren und anderen Tätigkeiten unterwegs Punkte sammelst, werden diese Punkte von der Waze Anwendung an den Server gesendet. Der Server erhält diese zurück und aktualisiert sie einmal am Tag in der Punktestatistik. Die [[client device|Anwendung]] zeigt dir deine Punkte an, die du erhältst. Sie zeigt aber auch jene an, die dir nicht angerechnet werden. Zum Beispiel, Du erhältst Punkte für das Bestätigen neuer Straßen (sogen. Pacman-Straßen) in dem Du die neuen Straßen mit den kleinen Punkten befährst. Tust Du das, so verwandelt sich Dein Standort-Cursor in ein Waze-Pacman und er beginnt die kleinen Punkte zu fressen. Aber Achtung, es kann aber auch sein, dass jemand eine Stunde vor Dir das gleiche gemacht und die neue Straße schon befahren und dadurch bestätigt hat. Da es die Punkte nur für den Ersten gibt, der eine neue Straße befährt, erhält er folglich auch diese Punkte und nicht du. Der Server wird dein Fahrt dann aussortier und bei der Punktevergabe nicht weiter berücksichtigen. Wenn Du Waze unterwegs neustartest, werden die aktuellen Punkte wieder von der Statistik des Servers heruntergeladen, allerdings ohne die Punkte, die Du für das vermeintliche Fressen der kleinen Punkte auf der neuen Straße gesehen hast. Am Ende des Tages werden alle Punkte auf dem Waze-Server aktualisiert und die Summe der Punkte ist so, wie es sein sollte. ==Punkte fressen(Munching/Pacman-Roads)== Auch wenn Deine gefahrenen Strecken im [[Mein Dashboard|Dashboard]] zu sehen sind, kann eine von dir bestätigte neue Straße immer noch als Pacman-Straße auf der Karte in der App erscheinen. Bis diese als normale Straße erscheint, kann es 2-7 Tage dauern. ==Städte Namen und Grenzen== Auf dem Waze Map-Editor sieht man die Städte mit farbigen Flächen hinterlegt. Diese farbigen Flächen werden durch die Benennung (City Namen) der Straßen definiert. Die Grenzen werden innerhalb von ein paar Tagen aktualisiert. Der Name der Stadt wird in der Mitte erscheinen. Der Name ist nicht immer da wo er sein sollte, dies hängt ab von der Zoom-Stufe und dem aktuellen Ort der Karte, den man anschaut. Bewegt man die Karte auf dem Display wandert auch der Name herum oder verschwindet teilweise ganz. Wird eine einzige Straße mit einem Stadtnamen belegt, liegt der Name auf diesem Segment in der Karte. Je mehr Straßen einem Stadtnamen zugeordnet werden, desto mehr Fläche hat auch der Namen, um sich auf der Karte zu bewegen. ==Automatische Straßen Updates von Waze== Je mehr Wazer (Waze-Benutzer) die Straßen befahren, desto mehr lernt Waze daraus. Waze verändert unbestätigte Straßen in der Geometrie und der Fahrtrichtung. Das Straßenbild verändert sich dadurch dynamisch, z.B. Straßen, sie ändern sich so von zwei- auf einspurig. Darüberhinaus lernt Waze, welche Abbiegungen erlaubt sind wenn die Wazer die Kreuzungen und Abbiegungen befahren. Bei Fehlern, z.B. aufgrund schlechtem GPS-Signals (speziell in Städten), falscher Abbiegungen oder des Befahrens von einspurigen Straßen in falscher Richtung ist Waze sehr konservativ, was diese Änderungen anbelangt. Für das Auslösen von automatischen Korrekturen bzw. Änderungen braucht zwischen 20 und 100 Fahrten, bevor diese erkannt und korrigiert werden. Dieser Prozess befindet sich im stetigen Wandel. * Lese im [http://world.waze.com/forum/ Forum] nach. * Benutze die [http://www.waze.com/forum/search.php Foren Such-Funktion] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 99833a28f2e12ed6edf97cf35e72b7c10558cc10 0 5 10367 10366 2016-06-19T20:33:51Z Wottem 21 117 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] == Einleitung == Wie Waze selbst ist diese Seite durch die Gemeinschaft entstanden und entwickelt sich kontinuierlich weiter. Viele hilfreiche Seiten existieren bereits unter [[Der Area Manager]], wie man den [[Der Waze Map-Editor|Karteneditor]] benutzt, Kartenfehler identifiziert und bearbeitet, Standards um Straßen zu klassifizieren und zu benennen und eine Seite über [[Häufig gestellte Fragen]]. Der Zweck dieser Seite ist es, Area-Managern und allen Benutzern zu helfen, eine Karte zu erstellen, welche für alle Waze-Endbenutzer während der Fahrt gut funktioniert. Auch kann so Mehraufwand durch nochmaliges Bearbeiten auf Grund von Fehlern oder Beschränkungen der Waze-Applikation vermieden werden. == Anleitungen == Im Wiki finden sich zahlreiche Anleitungen. Das Wichtigste am Anfang ist daher, sich mit den Anleitungen auseinanderzusetzen. Also lies die [[Anleitung zum Bearbeiten der Karte]] sorgfältig, bevor Du die Karte bearbeitest. == Hauptziele == === Benutzerfreundlichkeit === Wenn es um die Karte geht, ist das oberste Gebot: Für den Waze-Benutzer eine einfache Karte zu erstellen, der einfach zu folgen ist auf dem kleinen Bildschirm. Die Anweisungen sollen klar und sinnvoll sein und nur dann erscheinen, wenn sie auch gebraucht werden. === Einfachheit === Es soll nicht jede einzelne Spur auf der Karte eingezeichnet werden. Dies führt häufig nur zu unnötiger Komplexität, unlogischen Anweisungen beim Navigieren sowie unübersichtlichen Verhältnissen auf der Karte und schlussendlich zu unnötiger Mehrarbeit beim Korrigieren. === Erhaltung des bestehenden Zustandes === Durch das Befahren der Straßen werden in den Segmenten Informationen gespeichert, wie z.B. die Geschwindigkeit, welche für das optimale Routing benötigt wird. Wenn ein Segment gelöscht wird, gehen diese Informationen verloren. Wenn an einem unübersichtlichen Gewirr von Segmenten gearbeitet wird, ist es die bessere Wahl, diese weiterzuverwenden, anstatt bestehende zu löschen und neu zu zeichnen. === End-Kreuzung === Damit Waze aus einer Sackgasse herausnavigieren kann ist eine [[Erstellen und bearbeiten eines Segments#Kreuzung am Ende einer Sackgasse|End-Kreuzung]] zwingend nötig. Jedes Segment auf der Waze-Karte besitzt eine End-Kreuzung oder ist durch Kreuzungen mit anderen Segmenten verbunden. Dies ist die '''Goldene Regel'''. Dies gilt für alle Sackgassen und Segmente, die allein auf der Karte daliegen und nicht mit anderen Segmenten verbunden sind. Dies gilt auch für alle Straßentypen. Der Karteneditor fügt die Kreuzungen mittlerweile selbstständig hinzu. Solltest Du dennoch Straßen ohne End-Kreuzung vorfinden, füge sie bitte manuell hinzu. == In der Praxis == === In zwei Einbahnstraßen aufteilen oder nicht? === Es ist selten eine gute Idee, eine Straße, die nur durch Ein- und Ausfahrten auf eine Autobahn oder Hauptverkehrsstraße verbunden ist, in zwei Einbahnen aufzuteilen. An einer Kreuzung müssen auch nicht die Einmündungen aufgeteilt werden. Kreuzungen werden dadurch unnötig kompliziert, auf dem Bildschirm ist nichts mehr richtig zu erkennen, und die Anweisungen bei der Navigation sind verwirrend oder unsinnig. <br/>'''Eine Straße sollte in zwei Einbahnen aufgeteilt werden wenn:''' *Mindestens 5 Meter Abstand zwischen den Fahrspuren besteht. (Abgetrennt durch Beton, Blumentöpfe oder Beete, Bäume oder Grasflächen.) *Die GPS-Punkte liegen bei einer Zoomstufe von 100 Metern im Karteneditor genügend weit auseinander. <br/>'''Eine Straße sollte nicht in zwei Einbahnen aufgeteilt werden wenn:''' *Eine nicht befahrbare Fläche von weniger als 5 Metern zwischen den Fahrspuren besteht. *Eine längere Abbiegespur zwischen beiden Fahrtrichtungen existiert. *Viele Straßen kreuzen, die nur auf die nächstliegende Fahrbahn führen. *Google Maps oder andere Karten die Straßen so anzeigen. === Wie man zwei Einbahnen zu einer Fahrspur vereint === Wer eine Straße in zwei Fahrspuren aufteilt, sollte auch verstehen, was alles dazugehört, dies rückgängig zu machen. Es gibt leider keinen einfachen Weg zwei getrennte Fahrspuren wieder in eine zweispurige Straße zurückzuwandeln. Deshalb sollte man sich das Aufteilen gut überlegen. Wenn man eine Straße antrifft, die nicht aufgeteilt sein sollte, erkennt man dies sehr gut an der Summe der Fehlermeldungen der User. Dort wo die meisten Meldungen liegen brennt es in der Regel. Danach beginnt die hohe Kunst der Karten-Chirurgie am Waze-Karteneditor. Folgende Schritte sind zu erledigen: #Löschen der einen oder anderen Seite inkl. der Segmente, die beide Straßen verbinden. #Alle verwaisten Kreuzungen entfernen. #Richtungsänderungen an der verbleibenden Straße vornehmen. #Alle Abbiegeverbote kontrollieren. #Verbinden inkl. Abbiegeverbote aller Straßen, die in die verbleibende Straße münden. #Sicherstellen, dass die verleibende Straße korrekt in beide Richtungen verbunden ist. #Die Geometrie der zweispurigen Straße in die Mitte korrigieren. <br/>Damit man sich damit nicht zu viel Arbeit einheimst, sollte man vorher die richtige Straße auswählen, die verbleiben soll. Dies entscheidet man natürlich anhand der bereits verbundenen Segmente. Man kann auch übers Kreuz löschen damit man schneller vorwärts kommt. Nicht vergessen die verbleibende Straße wieder korrekt mit ihr selbst zu verbinden. === Autobahnen und Anschlüsse === Langstrecken-Navigation ist nicht möglich, wenn die Autobahnen nicht korrekt verbunden sind. Deshalb ist diesem Thema besondere Aufmerksamkeit zu widmen. Man kann sehr viel bewirken, wenn man diese korrekt erstellt. Besondere Überlegungen müssen bei eingeschränkt befahrbaren Straßen angestellt werden. Es kann bei unsorgfältiger Vorgehensweise auch mehr Schaden enstehen, als an normalen Quartierstraßen. ==== Straßen ==== Beschränkt zugängliche Straßen mit mehreren Spuren in beiden Richtungen, die durch ein Hindernis zwischen den Spuren abgetrennt sind und allein durch Rampen zugänglich sind, sollten fast immer in zwei Einbahnen aufgeteilt werden. Andere normale Straßen sollten meistens nicht aufgeteilt werden. ==== Ein- und Ausfahrten ==== Einfahrten sollten nach der Richtung in die sie führen benannt werden. Ausfahrten sollten nach der Ausfahrtnummer - wenn vorhanden - und auch der Beschilderung der Ausfahrten benannt werden. Dabei auch gleich die Verbindungen und Abbiegeverbote kontrollieren. *Es gibt in den länderspezifischen Wikis mehr Informationen zur Benennung. *Verstehe den Unterschied zwischen Ein- und Ausfahrten und ebenerdigen [[Abbiegespuren]] ==== Über- und Unterführungen ==== Erfahrungen haben gezeigt, dass es sinvoller ist einzelnen bestimmten Segmenten einen unterschiedlichen Level zu geben, als längeren Straßen die nicht durch Kreuzungen unterteilt sind. Autobahnen beispielsweise sollten generell auf Level 0 bleiben. Brücken die darüber führen Level 1. Über- oder Unterführungen sollten nicht Level 0 haben. Auch bei komplizierten Verzweigungen sollten die Levels den tatsächlichen Zustand widerspiegeln. Trifft man auf Segmente, die bereits im Level verändert wurden, muss man dem Drumherum besondere Aufmerksamkeit schenken, damit nicht fehlerhafte Levels entstehen an Straßen, die bereits korrekt erstellt wurden. In den meisten einfachen Fällen können Probleme beseitigt werden, wenn man den Level eines Segments ändert. Bei komplizierten Kreuzungen kann es hilfreich sein, eine Zeichung zu erstellen oder man schaut sich zuerst die höchst- oder tiefstliegendsten Segmente an, um sich Klarheit zu verschaffen. Gelegentlich kommt man auch an eine Kreuzung, wo die Levels auf den ersten Blick keinen Sinn ergeben. Es kann daher hilfreich sein, ein Segment durch eine Kreuzung zu unterteilen. Es bleibt dann zu hoffen, dass nicht jemand die Kreuzung löscht ohne sich vorher zu vergewissern, wieso die da ist. ==== Ebenen in Straßen ==== Egal welche Ebene eine Straße besitzt, wenn sie durch eine Kreuzung verbunden wird, wird die ganze Verzweigung navigierbar. Wenn man eine Über- oder Unterführung findet, die mit der darüber- oder darunterliegenden Straße durch eine Kreuzung verbunden ist, so ist diese Kreuzung zu löschen. Waze navigiert die Benutzer sonst von einer Brücke auf eine draunterliegende Straße (oder umgekehrt), was nicht sehr sinnvoll ist. Man vergewissert sich dabei zuerst, ob die Ebenen der kreuzenden Straßen und die Benennung der einzelnen Segmente gleich sind. Ansonsten kann die Kreuzung nicht gelöscht werden. Desweiteren kann man dies auch mit der Brücken-Funktion beheben. ==== Brücken-Funktion ==== Zwei Segmente, die über- oder unterführen auswählen und das Brückensymbol anklicken. Die beiden Segmente vereinen sich und der Level erhöht sich automatisch auf Level 1. Falls damit kein Erfolg erzielt wird muss man allf. die Segmente einzeln abtrennen und neu verbinden. Verbindest Du mit der Brücken-Funktion Segmente, die unterschiedliche Levels besitzen, erhöht sich der Level um einen höher, als das Segment mit dem höchsten Level. ==== Für Normalverkehr gesperrt oder zeitlich beschränkte Fahrverbote ==== Inzwischen unterstützt Waze auch [[Straßensperrungen und zeitlich beschränkte Fahrverbote|zeitlich beschränkte Fahrverbote]], Richtungswechsel zu bestimmten Zeiten oder Straßen, die für bestimmte Fahrzeuge reserviert sind. Diese Straßen haben manchmal eigene Einfahrten und führen parallel entlang normaler Straßen. Das Routing kann dadurch Anweisungen geben, die falsch sind oder gar tödlich enden können! Die einfachste Lösung war bisher, diese Straßen zu löschen, falls sie bereits erstellt wurden. Dies ist jedoch nicht erwünscht. Daher ist es sinnvoll, die erweiterten Eigenschaften möglichst überall hinzuzufügen. === Wann sind Ramps an Kreuzungen zu verwenden === Siehe hier [[Abbiegespuren]] === Wann ein Kreisverkehr erstellt werden soll === Wenn klar ist, wie man [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehre]] erstellt, ist es die richtige Zeit alle Kreisel, die nur aus einzelnen Straßen Segmenten gezeichnet wurden auszutauschen und durch richtige Kreisverlehre zu ersetzen. Das gleiche gilt für Kreisverkehre der Basis-Karte (Base Map), die ganz leicht an ihrer seltsam eckigen Form erkannt werden können. Spätestens nach dem Korrigieren wird einem klarwerden, wie die [[Erstellen und bearbeiten eines Kreisverkehrs|korrekten Ansagen]] bei der Navigation zustandekommen. === Richtung und Sperren von Straßen === '''Wozu sperrt man Segmente?''' Die "Sperren"-Funktion bewirkt gem. [[Häufig gestellte Fragen#Was ist eine gesperrte Straße im Waze Map-Editor.3F|den Häufig gestellten Fragen]] folgendes: *Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]]. *Zwingt das Routing, den verbundenen Segmenten zu folgen und macht es nahezu unmöglich, gegen die definierte Fahrtrichtung zu Routen. '''Wann sperrt man Segmente?''' ''[[Wichtig: Unvollständige Segmente werden nicht gesperrt.]]'' Grundsätzlich bleiben Straßen frei. Waze lebt von den Beiträgen vieler, und jeder soll die Möglichkeit behalten, aktuelle Änderungen an Straßen schnell und einfach einzutragen. Sperren sollten also nur auf wichtigen Straßen vorgenommen werden, wo durch die Bearbeitung durch Einsteiger gravierende Auswirkungen, insbesondere auf den überregionalen Verkehr zu befürchten sind. Folgende Straßen müssen gelockt werden, wenn sie vollständig bearbeitet sind: *Autobahnen samt den zugehörigen Auf- und Abfahrten: Level 4 oder 5 *Bundesstraßen: Level 3 Wenn diese Straßen durch einen Editor niedrigen Ranges erstellt oder bearbeitet wurden, fordert er die Sperrung mit dem richtigen Level im Forum an. '''Informiere Dich in den länderspezifischen Wikis über die Gegebenheiten im betreffenden Land!''' === Konnektivität === Nur weil sich zwei Segmente an einer Kreuzung berühren, heißt dies noch nicht, dass sie auch korrekt miteinander verbunden sind. Abbiegeverbote kontrollieren! === Unnötige Kreuzungen === Unnötige Kreuzungen sind zu entfernen, da sie oft zu fehlerhaften Verbindungen und falschen Straßennamen führen. Zudem sind sie für das [[Wie Waze Routen kalkuliert|Routing]] nicht von Vorteil, da pro Kreuzung ein Zuschlag von 5 Sekunden zur Fahrzeitberechnung addiert wird. Ausnahmen bilden Orts- oder Landesgrenzen, oder wenn man in Kürze eine Straße mit einer Kreuzung verbindet. Wenn Kreuzungen entfernt werden, muss darauf geachtet werden, dass die Segmente die gleichen Eigenschaften besitzen. Andernfalls kann die Kreuzung nicht entfernt werden. Kreuzungen auf Straßen mit der Eigenschaft "Unbekannt" können aus Sicherheitsgründen nicht gelöscht werden. Straßen in Richtung ändern und nach dem Entfernen der Kreuzung allf. wieder auf "Unbekannt" setzen. == Neue Straßen == === Aufzeichnen mit der Waze-App === Nach dem Aufzeichnen muss die Straße im Editor bearbeitet werden. Aufgezeichnete und unbearbeitete Straßen tauchen zwar in der App auf, sie werden aber nicht für das Routing benutzt. '''Man sollte diesen Anweisungen folgen:''' #Geometrie ausrichten anhand der Luftaufnahme, sofern diese am richtigen Ort ist in der Gegend. Dies sollte mit der Ebene GPS-Punkte geprüft werden. Kanten und Ecken abrunden wo nötig. #Korrekter Straßentyp und Name anhand der Definition des Landes einfügen. #Die korrekte Fahrtrichtung bestimmen. #Kreuzungen hinzufügen und Straßen korrekt verbinden. <br/>Wenn mit dem Bearbeiten einer neuen Straße (rot) begonnen wird, wird die Straße ohne Typenänderung weiß erscheinen. Nach dem nächsten Kartenupdate von Waze, wird diese dann auf der Echtzeit-Karte und der Waze-App zu sehen sein. Daher ist es nicht sehr hilfreich, eine unfertige Straße zu hinterlassen. Solange sie rot ist, merkt mann noch, dass die Straße bearbeitet werden muss. Aber sobald sie weiß wird, kann sie im Karteneditor nicht mehr so schnell identifiziert werden. Wenn sie nur weiß ist und auch einen Straßennamen hat, mag dies gut aussehen, aber Waze weiß vielleicht noch nicht, dass die Straße befahren werden kann. == Parkings und Parkplätze == Das Zuordnen eines Parkplatzes und dessen Straßen dient zwei Zwecken: *es erlaubt Waze eine Tür-zu-Tür-Navigation innerhalb des Parkplatzes *es erlaubt Waze von einer Hauptstraße weg zu navigieren, um fehlerhafte Verkehrsmeldungen zu vermeiden ==== Gebrauch des "Parkplatz"-Straßentyps ==== "Parkplatz" ermöglicht das Erstellen von Parkplätzen und verhindert gleichzeitig, dass der Routing-Server diese für die Navigation miteinbezieht. Damit nicht durch Parkplätze geroutet wird, hat Waze den Routing-Algorithmus im Juni 2012 geändert. Jedes Segment, das sich innerhalb eines Parkplatzes befindet ist daher als "Parkplatz" zu definieren. ==== Einkaufszentren ==== Wenn ein Parkplatz eines Einkaufszentrums erstellt wird, sollten Haupteinfahrten und die wichtigsten Verbindungen erstellt werden, Verbindungen zwischen verschiedenen Parzellen eines Parkplatzes und entlang der Geschäfte. Die meistgebrauchten Spuren sollten dabei miteinbezogen werden. Am wichtigsten sind hier Benutzerfreundlichkeit und Einfachheit. Es macht keinen Sinn, jedes einzelne Parkfeld mit einem Segment zu bestücken, dies lässt die Karte auf der App nur unübersichtlich aussehen. ==== Kleinere Parkplätze ==== Parkplätze, die einer kleinen Anzahl von Unternehmen dienen, sollten minimal sein. Genug, um dem Fahrer richtige Richtungen, Ein- und Ausfahrten zu zeigen und den Weg zu einem Geschäft. Manchmal reicht ein einziges paralleles Segment. ==== Durchfahrts-Parkplätze ==== Diese sollten nicht zu viele Einbahnen enthalten und am besten mit einer Einbahn als Schlaufe durch den Parkplatz führen. Man bedenke dabei, dass sich eine [[WME Schnellstart-Anleitung#Straßen-Schlaufen|Straße]] nicht mit sich selbst verbindet. ==== Parkhäuser ==== Wenn ein Parkhaus nur eine Ein- und Ausfahrt besitzt, sollte diese mindestens auf der Karte erscheinen. Ein einzelnes zweispuriges Segment reicht aus, da im Parkhaus meistens kein GPS-Signal vorhanden ist. Der Straßentyp ist "Parkplatz" und das Parkhaus kann mit einem Orientierungspunkt versehen werden. Besitzt das Parkhaus separate Ein- und Ausfahrten, so sollte eine Durchfahrt ermöglicht werden. Dazu reicht in den meisten Fällen ein einziges Segment. Es ist nicht nötig, jedes Stockwerk des Parkhauses darzustellen, dies macht die Karte nur unnötig unübersichtlich. == Unterdrücken von Verkehrsmeldungen und Kartenfehlern == Straßensegmente vom Typ "Parkplatzstraße" verhindern die Erstellung von Staumeldungen, und von Kartenfehlern für "fehlende Straße". == Klassifizierung von Kreuzungen == Verschiedene Arten von Kreuzungen haben [[Classification of crossings|Standard-Möglichkeiten]], um diese zu bearbeiten. Interessant sind auch diese Seiten:<br/>[[Kreuzungen]]<br/>[[Abbiegespuren]] <center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br/>[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 59dbe94008b90d8be23a5a374ce0d5756b769be6 0 6 10385 10384 2016-06-19T20:33:52Z Wottem 21 17 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Neue Straßen, die noch nicht auf der Karte vorhanden sind, können über die Waze-Anwendung aufgezeichnet werden. Benutze dafür die Funktion "Zeichne auf" im Menü "Melden" und bestätige das Popup "Zeichne Straße auf". [[Image:Nehme auf.PNG]] [[Image:Nehme strasse auf.PNG]] '''Verwende diese Funktion nur, wenn Du auf Straßen fährst, die noch nicht auf der Karte existieren! ''' <br> <br> Waze zeichnet bei ungenauem GPS-Signal Straßen auf, wo schon welche vorhanden sind, da die Anwendung in diesem Fall der Meinung ist, dass man sich nicht auf einer existierenden Straße befindet. Dies führt zu unerwünschten Korrekturen durch die Editoren oder Area-Manager. Es ist auch zu beachten, dass Waze bei fehlender oder schlechter Netz-Abdeckung die Karte nicht in die Anwendung herunterladen kann. Das heißt: Es ist keine Karte sichtbar, aber sie ist trotzdem bereits vorhanden. Auch in diesem Moment können Straßen aufgezeichnet werden. Daher Vorsicht bei der Aufzeichnung! Die neu aufgezeichneten Straßen erscheinen innerhalb kurzer Zeit im Map-Editor, wo du diese weiterbearbeiten kannst. Bitte erledige dies in möglichst kurzer Zeit, sonst wird die Karte nicht erweitert und die Benutzer können nicht von deiner Arbeit profitieren. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 12c2557ca686823360676b62f3c78df6c9dd66c7 0 7 10478 10477 2016-06-19T20:34:03Z Wottem 21 92 Versionen importiert wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen * <span style="color:RoyalBlue;">'''Zufahrtsstraße'''</span> => werden nicht verwendet! ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. * Ausfahrt Zürich Flughafen, Ausfahrt Bülach-Nord * Einfahrt > Basel Bern Luzern, Einfahrt > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Einfahrt > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Sie dürfen keine Verbindung zu existierenden Strassen haben und sollen mit Level -5 versehen werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 5 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 134947e638090184a8834389fbd76e9dcd38cf0c 0 8 10597 10596 2016-06-19T20:34:14Z Wottem 21 118 Versionen importiert wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Blitzer einpflegen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Base Map 1.0]] * [[Der Area Manager]] ==Seiten auf Englisch== * [[How Waze determines turn / keep / exit maneuvers]] * [[Limited Access Interchange Style Guide]] * [[Navigation problems]] * [[Small Detour Prevention Mechanism]] * [[Community Plugins, Extensions and Tools]] * [[Classification of crossings]] * [[Scheduled_Restrictions|Scheduled Restrictions]] * [[Battery Usage]] ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Hilf mit Waze zu verbessern]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] 7950fcfa1f50ba667f8c9f8f869300183b4f76db 0 9 10608 10607 2016-06-19T20:34:14Z Wottem 21 10 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [http://www.waze.com/forum/ Offizielles Ankündigungs- und Diskussionsforum] Waze benutzt für das Forum die Forensoftware phpBB von einem Drittanbieter. Du kannst das Forum als Gast durchforschen, aber Du musst dich mit deinem Waze Account anmelden um Kommentare zu schreiben. Eine Anmeldung erlaubt auch: * Symbole für Neue Nachricht. * Link für ungelesene Nachrichten. * Private Kommunikation (PM). * Eine Thema zu Abonnieren (Du wirst auf eine Nachricht in einem deiner Posts per Mail hingewiesen). Das Forum unterstützt Tapatalk für iPhone. Tapatalk ist eine kostenpflichtige Applikation aber es gibt auch eine [http://itunes.apple.com/us/app/tapatalk-ro-forum-app/id335769233?mt=8# freie Version nur mit Lesezugriff]. Das Forum kann auch als [[RSS Feeds|RSS-Feed]] abonniert werden. Das Forum besitzt ein Suchfunktion, indexiert allerdings nicht die meistgebräuchlichsten Wörter. Wenn das ein Problem darstellen sollte gibt es die Möglichkeit [[Discussion Forums/Search in forums|mit Google im Forum zu suchen]]. Der direkte Login-Link lautet: https://www.waze.com/forum/ucp.php Hier findest Du die Foren [http://world.waze.com/forum/faq.php FAQ] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 4d64e60996bf637f3aff55c828eec848149e47ef 0 10 10649 10648 2016-06-19T20:34:23Z Wottem 21 40 Versionen importiert wikitext text/x-wiki [[Strassen und Orte benennen in der Schweiz|Zurück zu Strassen und Orte benennen in der Schweiz]] ==Segmente und Kreuzungen== [[Image:Segmente und Kreuzungen.png]] '''Was ist ein Segment?''' In der Geometrie eine Linie, die durch zwei Endpunkte begrenzt ist. Im [[Der Waze Map-Editor|Kartenditor]], benützen wir [[Erstellen und bearbeiten eines Segments|Segmente]] um neue Strassen zu zeichnen. Wie oben schon gesagt hat das Segment eine Begrenzung. In unserem Fall ist dies eine [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|Kreuzung]]. * In der Schweiz richtet sich die Klassifizierug nach der Beschilderung. Mehr Informationen zur Benennung und Zuordnung findest Du hier im [[Strassen und Orte benennen in der Schweiz|Wiki Schweiz]] <b>Bitte beachte auch, dass die Klassifizierung von Land zu Land unterschiedlich ist. Deshalb ist es wichtig, bei der Bearbeitung im Ausland die länderspezifischen Wikis zu kennen.</b> ==Segment Typen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "ß" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! ===Fernstrassen=== '''Autobahn [[Image:RoadBlue.png|200px]]''' Als Freeway wird in der Schweiz eine Autobahn mit Richtungsgetrennten Spuren ohne Ampeln und Stoppschilder definiert. Autobahnen sind nur durch Ein- und Ausfahrten zugänglich. Strassen wie, Hauptstrassen, Nebenstrassen etc. können nicht direkt auf eine Autobahn verbunden sein. Ausnahmen bilden Zufahrten für Schutz und Rettung, welche aber für den Pendler nicht navigierbar sein sollen. Viele Nationalstrassen führen über Autobahnen, in all diesen Fällen gelten die Autobahn Bezeichnungen vorrangig. Eine Liste aller Autobahnen in der Schweiz gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] Die Farbe aller Autobahnschilder und Wegweiser in der Schweiz ist grün. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Bundesstraße [[Image:Majorhighwayseg.png |200px]]''' Als Bundesstraße definieren wir alle Schnell- und Autostrassen, die nicht Autobahnen sind. Autostrassen sind in der Schweiz wie Autobahnen - abgesehen von wenigen Autobahnzubringern - immer kreuzungsfrei angelegt, aber im Gegensatz zu Autobahnen selten richtungsgetrennt und meistens einspurig. Eine Liste aller Autostrassen gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] Die Autostrassen sind auch grün ausgeschildert. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Landesstraße [[Image:RoadYell.png |200px]]''' Als Landesstraße definieren wir alle nummerierten Hauptstrassen und Nationalstrassen in der Schweiz. Die Nummerierung richtet sich nach der Beschilderung. An Ortsausfahrten sind die Nummern unter dem Hauptstrassen- oder Ortsschild ersichtlich. Eine Liste aller Nummerierten Hauptstrassen gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] Eine Liste aller Nationalstrassen gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Rampe [[Image:Ramp.png |200px]]''' Rampe wird für Ein- und Ausfahrten auf Autobahnen verwendet. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Strassen=== Auch in den Städten finden wir die verschiedensten Strassentypen: ---- '''Hauptstraße [[Image:Primary street.png|200px]]''' Als Hauptstraße ordnen wir alle Strassen nach der Beschilderung. [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Straße [[Image:Street.png|200px]]''' Als Straße definieren wir alle Strassen und Nebenstrassen, wie Quartierstrassen oder sonstige, die für den Normalverkehr uneingeschränkt befahrbar sind. Diese können Einbahnstrassen oder auch Strassen mit Gegenverkehr sein. Nebenstrassen sind weiss ausgeschildert. Sie werden auch auf Landstrassen verwendet. [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Normale Strasse: [[Image:RoadPicN4.jpg|400px]] ---- '''Zufahrtsstraße [[Image:Service road.png|200px]]''' Zufartsstraßen werden nicht verwendet. ---- '''Feldweg / 4x4 Weg [[Image:Service road.png|200px]]''' Als Feldweg / 4x4 Weg definieren wir alle Land- und Forstwirtschaftlichen Strassen, Waldstrassen, Kies- und Feldwege die keinen Strassenbelag aufweisen und durch den Normalverkehr befahren werden dürfen. [[Image:RoadPicN6.jpg |400px]] ---- '''Parkplatz [[Image:Service road.png|200px]]''' Als Parkplatz definieren wir grosse Parkplätze, Parkplätze innerhalb Raststätten, Strassen an Parkplätze oder Siedlungen mit Parkplätzen. [[Image:RoadPicN7.jpg |400px]] ---- '''Privatstraße [[Image:Service road.png|200px]]''' Als Privatstraße werden alle Strassen definiert, die auch so bezeichnet oder beschildert sind. Ferner sind sie zu verwenden, wo ein Routing ausgeschlossen werden soll für den Normalverkehr (Zubringerdienst etc.). Lies dazu das Thema [[Fußwege und Privatstraßen]]. ---- '''Fußweg [[Image:Service road.png|200px]]''' Als Fußweg sind alle Fusswege zu definieren. '''Alle Fusswege dürfen keine Verbindung zwischen zwei routbaren Strassen besitzen.''' Lies dazu das Thema [[Fußwege und Privatstraßen]]. [[Image:RoadPicN9.jpg |400px]] ---- '''Fußgängerzone[[Image:Service road.png|200px]]''' Als Fußgängerzone definieren wir Fussgängerzonen, Uferwege. '''Alle Fusswege dürfen keine Verbindung zwischen zwei routbaren Strassen besitzen.''' [[Image:RoadPicN10.jpg|400px]] ---- '''Treppe [[Image:Service road.png|200px]]''' Als Treppe sind alle Treppenwege zu bezeichnen. '''Alle Fusswege dürfen keine Verbindung zwischen zwei routbaren Strassen besitzen.''' [[Image:RoadPicN11.jpg|400px]] ---- '''Eisenbahn [[Image:Service road.png|200px]]''' Als Eisenbahn sind die Eisenbahnlinien zu definieren. Diese sind in der App jedoch nicht sichtbar. Sie sollen auch nicht über die App aufgezeichnet werden, sondern im Waze Map-Editor hinzugefügt werden. Sie müssen auch mit Level -5 versehen werden und dürfen keine Verbindungen auf bestehende Strassen aufweisen. Die Benennung richtet sich nach dem Namen der Bahn. ---- '''Landebahn [[Image:Service road.png|200px]]''' Als Landebahn können Lande- und Rollbahnen eingezeichnet werden (Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten und jeden Weg darauf einzuzeichnen, Orientierungspunkt (Flughafen) reicht vollkommen aus!) Wieder: keine Verbindung zum normalen Strassennetz! <br> [[Strassen und Orte benennen in der Schweiz|Zurück zu Strassen und Orte benennen in der Schweiz]] [[Category:Schweiz]] ead7f43bb5e420abaf772cbe44f3b865ef033f83 0 11 10701 10700 2016-06-19T20:35:10Z Wottem 21 51 Versionen importiert wikitext text/x-wiki [[Strassen_und_Orte_benennen_in_der_Schweiz|Zurück zu Strassen und Orte benennen in der Schweiz]] ===Orte Schweiz Stand: 27.01.2014 / 01.53h=== {| class="wikitable" | style="background-color: #99FF99;"| Fertig |- | style="background-color: #d05454;"| Nicht fertig/kontrolliert |} {| class="wikitable" |- ! Ort !! Status |- |Aadorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Aarau || style="width: 30%; background-color: #99FF99;"|Argus |- |Aarau Rohr || style="width: 30%; background-color: #99FF99;"|Argus |- |Aarberg || style="width: 30%; background-color: #d05454;"| |- |Aarburg || style="width: 30%; background-color: #99FF99;"|Argus |- |Aarwangen || style="width: 30%; background-color: #99FF99;"|Argus |- |Aathal-Seegräben || style="width: 30%; background-color: #d05454;"| |- |Aawangen || style="width: 30%; background-color: #99FF99;"|Argus |- |Abländschen || style="width: 30%; background-color: #d05454;"| |- |Abtwil AG || style="width: 30%; background-color: #d05454;"| |- |Abtwil SG || style="width: 30%; background-color: #d05454;"| |- |Achseten || style="width: 30%; background-color: #d05454;"| |- |Aclens || style="width: 30%; background-color: #d05454;"| |- |Acquarossa || style="width: 30%; background-color: #d05454;"| |- |Adelboden || style="width: 30%; background-color: #d05454;"| |- |Adetswil || style="width: 30%; background-color: #d05454;"| |- |Adligenswil || style="width: 30%; background-color: #d05454;"| |- |Adlikon b. Andelfingen || style="width: 30%; background-color: #d05454;"| |- |Adlikon b. Regensdorf || style="width: 30%; background-color: #d05454;"| |- |Adliswil || style="width: 30%; background-color: #d05454;"| |- |Aedermannsdorf || style="width: 30%; background-color: #d05454;"| |- |Aefligen || style="width: 30%; background-color: #d05454;"| |- |Aegerten || style="width: 30%; background-color: #d05454;"| |- |Aesch (Neftenbach) || style="width: 30%; background-color: #d05454;"| |- |Aesch BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Aesch LU || style="width: 30%; background-color: #d05454;"| |- |Aesch ZH || style="width: 30%; background-color: #d05454;"| |- |Aeschau || style="width: 30%; background-color: #d05454;"| |- |Aeschi b. Spiez || style="width: 30%; background-color: #d05454;"| |- |Aeschi SO || style="width: 30%; background-color: #d05454;"| |- |Aeschiried || style="width: 30%; background-color: #d05454;"| |- |Aeschlen b. Oberdiessbach || style="width: 30%; background-color: #d05454;"| |- |Aeschlen ob Gunten || style="width: 30%; background-color: #d05454;"| |- |Aetigkofen || style="width: 30%; background-color: #d05454;"| |- |Aetingen || style="width: 30%; background-color: #d05454;"| |- |Aettenschwil || style="width: 30%; background-color: #d05454;"| |- |Aeugst am Albis || style="width: 30%; background-color: #d05454;"| |- |Aeugstertal || style="width: 30%; background-color: #d05454;"| |- |Affeltrangen || style="width: 30%; background-color: #d05454;"| |- |Affoltern am Albis || style="width: 30%; background-color: #d05454;"| |- |Affoltern im Emmental || style="width: 30%; background-color: #d05454;"| |- |Agarn || style="width: 30%; background-color: #d05454;"| |- |Agarone || style="width: 30%; background-color: #d05454;"| |- |Agasul || style="width: 30%; background-color: #d05454;"| |- |Agiez || style="width: 30%; background-color: #d05454;"| |- |Agno || style="width: 30%; background-color: #d05454;"| |- |Agra || style="width: 30%; background-color: #d05454;"| |- |Agriswil || style="width: 30%; background-color: #d05454;"| |- |Aigle || style="width: 30%; background-color: #d05454;"| |- |Aïre || style="width: 30%; background-color: #d05454;"| |- |Aire-la-Ville || style="width: 30%; background-color: #d05454;"| |- |Airolo || style="width: 30%; background-color: #d05454;"| |- |Alberswil || style="width: 30%; background-color: #d05454;"| |- |Albeuve || style="width: 30%; background-color: #d05454;"| |- |Albinen || style="width: 30%; background-color: #d05454;"| |- |Albligen || style="width: 30%; background-color: #d05454;"| |- |Albonago || style="width: 30%; background-color: #d05454;"| |- |Alchenflüh || style="width: 30%; background-color: #d05454;"| |- |Alchenstorf || style="width: 30%; background-color: #d05454;"| |- |Aldesago || style="width: 30%; background-color: #d05454;"| |- |Algetshausen || style="width: 30%; background-color: #d05454;"| |- |Alikon || style="width: 30%; background-color: #d05454;"| |- |Allaman || style="width: 30%; background-color: #d05454;"| |- |Alle || style="width: 30%; background-color: #d05454;"| |- |Allens || style="width: 30%; background-color: #d05454;"| |- |Allenwinden || style="width: 30%; background-color: #d05454;"| |- |Allerheiligenberg || style="width: 30%; background-color: #d05454;"| |- |Allmendingen b. Bern || style="width: 30%; background-color: #d05454;"| |- |Allschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Almens || style="width: 30%; background-color: #d05454;"| |- |Alosen || style="width: 30%; background-color: #d05454;"| |- |Alp Grüm || style="width: 30%; background-color: #d05454;"| |- |Alpnach Dorf || style="width: 30%; background-color: #d05454;"| |- |Alpnachstad || style="width: 30%; background-color: #d05454;"| |- |Alpthal || style="width: 30%; background-color: #d05454;"| |- |Alt St. Johann || style="width: 30%; background-color: #d05454;"| |- |Altbüron || style="width: 30%; background-color: #d05454;"| |- |Altdorf SH || style="width: 30%; background-color: #d05454;"| |- |Altdorf UR || style="width: 30%; background-color: #d05454;"| |- |Alten || style="width: 30%; background-color: #d05454;"| |- |Altendorf || style="width: 30%; background-color: #d05454;"| |- |Altenrhein || style="width: 30%; background-color: #d05454;"| |- |Alterswil FR || style="width: 30%; background-color: #d05454;"| |- |Alterswilen || style="width: 30%; background-color: #d05454;"| |- |Altikon || style="width: 30%; background-color: #d05454;"| |- |Altishausen || style="width: 30%; background-color: #d05454;"| |- |Altishofen || style="width: 30%; background-color: #d05454;"| |- |Altnau || style="width: 30%; background-color: #d05454;"| |- |Altstätten SG || style="width: 30%; background-color: #d05454;"| |- |Altwis || style="width: 30%; background-color: #d05454;"| |- |Alvaneu Bad || style="width: 30%; background-color: #d05454;"| |- |Alvaneu Dorf || style="width: 30%; background-color: #d05454;"| |- |Alvaschein || style="width: 30%; background-color: #d05454;"| |- |Am Bach (Avers) || style="width: 30%; background-color: #d05454;"| |- |Ambrì || style="width: 30%; background-color: #d05454;"| |- |Amden || style="width: 30%; background-color: #d05454;"| |- |Aminona || style="width: 30%; background-color: #d05454;"| |- |Amlikon || style="width: 30%; background-color: #d05454;"| |- |Ammerswil AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Ammerzwil BE || style="width: 30%; background-color: #d05454;"| |- |Amriswil || style="width: 30%; background-color: #d05454;"| |- |Amsoldingen || style="width: 30%; background-color: #d05454;"| |- |Amsteg || style="width: 30%; background-color: #d05454;"| |- |Andeer || style="width: 30%; background-color: #d05454;"| |- |Andelfingen || style="width: 30%; background-color: #d05454;"| |- |Andermatt || style="width: 30%; background-color: #d05454;"| |- |Andhausen || style="width: 30%; background-color: #d05454;"| |- |Andiast || style="width: 30%; background-color: #d05454;"| |- |Andwil SG || style="width: 30%; background-color: #d05454;"| |- |Andwil TG || style="width: 30%; background-color: #d05454;"| |- |Anglikon || style="width: 30%; background-color: #d05454;"| |- |Anières || style="width: 30%; background-color: #d05454;"| |- |Anwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Anzère || style="width: 30%; background-color: #d05454;"| |- |Anzonico || style="width: 30%; background-color: #d05454;"| |- |Appenzell || style="width: 30%; background-color: #d05454;"| |- |Apples || style="width: 30%; background-color: #d05454;"| |- |Aproz (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Aquila || style="width: 30%; background-color: #d05454;"| |- |Aran || style="width: 30%; background-color: #d05454;"| |- |Aranno || style="width: 30%; background-color: #d05454;"| |- |Arbaz || style="width: 30%; background-color: #d05454;"| |- |Arbedo || style="width: 30%; background-color: #d05454;"| |- |Arboldswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Arbon || style="width: 30%; background-color: #d05454;"| |- |Arcegno || style="width: 30%; background-color: #d05454;"| |- |Arch || style="width: 30%; background-color: #d05454;"| |- |Arconciel || style="width: 30%; background-color: #d05454;"| |- |Ardez || style="width: 30%; background-color: #d05454;"| |- |Ardon || style="width: 30%; background-color: #d05454;"| |- |Areuse || style="width: 30%; background-color: #d05454;"| |- |Arezen || style="width: 30%; background-color: #d05454;"| |- |Argnoud (Ayent) || style="width: 30%; background-color: #d05454;"| |- |Arisdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Aristau || style="width: 30%; background-color: #d05454;"| |- |Arlesheim || style="width: 30%; background-color: #d05454;"| |- |Arnegg || style="width: 30%; background-color: #d05454;"| |- |Arnex-sur-Nyon || style="width: 30%; background-color: #d05454;"| |- |Arnex-sur-Orbe || style="width: 30%; background-color: #d05454;"| |- |Arni AG || style="width: 30%; background-color: #d05454;"| |- |Arni BE || style="width: 30%; background-color: #d05454;"| |- |Arogno || style="width: 30%; background-color: #d05454;"| |- |Arolla || style="width: 30%; background-color: #d05454;"| |- |Arosa || style="width: 30%; background-color: #d05454;"| |- |Arosio || style="width: 30%; background-color: #d05454;"| |- |Arth || style="width: 30%; background-color: #d05454;"| |- |Arveyes || style="width: 30%; background-color: #d05454;"| |- |Arvigo || style="width: 30%; background-color: #d05454;"| |- |Arvillard (Salins) || style="width: 30%; background-color: #d05454;"| |- |Arzier || style="width: 30%; background-color: #d05454;"| |- |Arzo || style="width: 30%; background-color: #d05454;"| |- |Ascharina || style="width: 30%; background-color: #d05454;"| |- |Ascona || style="width: 30%; background-color: #d05454;"| |- |Asp || style="width: 30%; background-color: #d05454;"| |- |Assens || style="width: 30%; background-color: #d05454;"| |- |Astano || style="width: 30%; background-color: #d05454;"| |- |Asuel || style="width: 30%; background-color: #d05454;"| |- |Athenaz (Avusy) || style="width: 30%; background-color: #d05454;"| |- |Attalens || style="width: 30%; background-color: #d05454;"| |- |Attelwil || style="width: 30%; background-color: #d05454;"| |- |Attikon || style="width: 30%; background-color: #d05454;"| |- |Attinghausen || style="width: 30%; background-color: #d05454;"| |- |Attiswil || style="width: 30%; background-color: #d05454;"| |- |Au SG || style="width: 30%; background-color: #d05454;"| |- |Au TG || style="width: 30%; background-color: #d05454;"| |- |Au ZH || style="width: 30%; background-color: #d05454;"| |- |Aubonne || style="width: 30%; background-color: #d05454;"| |- |Auboranges || style="width: 30%; background-color: #d05454;"| |- |Auddes-sur-Riddes || style="width: 30%; background-color: #d05454;"| |- |Auenstein || style="width: 30%; background-color: #99FF99;"|Argus |- |Augio || style="width: 30%; background-color: #d05454;"| |- |Augst BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Aumont || style="width: 30%; background-color: #d05454;"| |- |Auressio || style="width: 30%; background-color: #d05454;"| |- |Aurigeno || style="width: 30%; background-color: #d05454;"| |- |Auslikon || style="width: 30%; background-color: #d05454;"| |- |Ausserberg || style="width: 30%; background-color: #d05454;"| |- |Ausserbinn || style="width: 30%; background-color: #d05454;"| |- |Ausserferrera || style="width: 30%; background-color: #d05454;"| |- |Auswil || style="width: 30%; background-color: #d05454;"| |- |Autafond || style="width: 30%; background-color: #d05454;"| |- |Autavaux || style="width: 30%; background-color: #d05454;"| |- |Autigny || style="width: 30%; background-color: #99FF99;"|Argus |- |Auvernier || style="width: 30%; background-color: #d05454;"| |- |Auw || style="width: 30%; background-color: #d05454;"| |- |Avegno || style="width: 30%; background-color: #d05454;"| |- |Aven || style="width: 30%; background-color: #d05454;"| |- |Avenches || style="width: 30%; background-color: #d05454;"| |- |Avry-devant-Pont || style="width: 30%; background-color: #d05454;"| |- |Avry-sur-Matran || style="width: 30%; background-color: #d05454;"| |- |Avully || style="width: 30%; background-color: #d05454;"| |- |Axalp || style="width: 30%; background-color: #d05454;"| |- |Ayent || style="width: 30%; background-color: #d05454;"| |- |Ayer || style="width: 30%; background-color: #d05454;"| |- |Azmoos || style="width: 30%; background-color: #d05454;"| |- |Baar || style="width: 30%; background-color: #d05454;"| |- |Baar (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Bäch SZ || style="width: 30%; background-color: #d05454;"| |- |Bachenbülach || style="width: 30%; background-color: #d05454;"| |- |Bächli (Hemberg) || style="width: 30%; background-color: #d05454;"| |- |Bachs || style="width: 30%; background-color: #d05454;"| |- |Bad Ragaz || style="width: 30%; background-color: #d05454;"| |- |Bad Zurzach || style="width: 30%; background-color: #99FF99;"|Argus |- |Baden || style="width: 30%; background-color: #d05454;"| |- |Baldegg || style="width: 30%; background-color: #d05454;"| |- |Baldingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Balerna || style="width: 30%; background-color: #d05454;"| |- |Balgach || style="width: 30%; background-color: #d05454;"| |- |Ballaigues || style="width: 30%; background-color: #d05454;"| |- |Ballens || style="width: 30%; background-color: #d05454;"| |- |Ballmoos || style="width: 30%; background-color: #d05454;"| |- |Ballwil || style="width: 30%; background-color: #d05454;"| |- |Balm b. Günsberg || style="width: 30%; background-color: #d05454;"| |- |Balm b. Messen || style="width: 30%; background-color: #d05454;"| |- |Balmberg || style="width: 30%; background-color: #d05454;"| |- |Balsthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Balterswil || style="width: 30%; background-color: #d05454;"| |- |Baltschieder || style="width: 30%; background-color: #d05454;"| |- |Banco || style="width: 30%; background-color: #d05454;"| |- |Bangerten || style="width: 30%; background-color: #d05454;"| |- |Bänk (Dägerlen) || style="width: 30%; background-color: #d05454;"| |- |Bannwil || style="width: 30%; background-color: #d05454;"| |- |Bärau || style="width: 30%; background-color: #d05454;"| |- |Barbengo || style="width: 30%; background-color: #d05454;"| |- |Barberêche || style="width: 30%; background-color: #d05454;"| |- |Bäretswil || style="width: 30%; background-color: #d05454;"| |- |Bargen BE || style="width: 30%; background-color: #d05454;"| |- |Bargen SH || style="width: 30%; background-color: #d05454;"| |- |Bäriswil BE || style="width: 30%; background-color: #d05454;"| |- |Barmelweid || style="width: 30%; background-color: #d05454;"| |- |Bärschwil || style="width: 30%; background-color: #d05454;"| |- |Barzheim || style="width: 30%; background-color: #d05454;"| |- |Basadingen || style="width: 30%; background-color: #d05454;"| |- |Basel || style="width: 30%; background-color: #99FF99;"|Argus |- |Basse-Nendaz || style="width: 30%; background-color: #d05454;"| |- |Bassecourt || style="width: 30%; background-color: #d05454;"| |- |Bassersdorf || style="width: 30%; background-color: #d05454;"| |- |Bassins || style="width: 30%; background-color: #d05454;"| |- |Bätterkinden || style="width: 30%; background-color: #d05454;"| |- |Bättwil || style="width: 30%; background-color: #d05454;"| |- |Bauen || style="width: 30%; background-color: #d05454;"| |- |Baulmes || style="width: 30%; background-color: #d05454;"| |- |Bauma || style="width: 30%; background-color: #d05454;"| |- |Bavois || style="width: 30%; background-color: #d05454;"| |- |Bazenheid || style="width: 30%; background-color: #d05454;"| |- |Beatenberg || style="width: 30%; background-color: #d05454;"| |- |Beckenried || style="width: 30%; background-color: #d05454;"| |- |Bedano || style="width: 30%; background-color: #d05454;"| |- |Bedigliora || style="width: 30%; background-color: #d05454;"| |- |Bedretto || style="width: 30%; background-color: #d05454;"| |- |Beggingen || style="width: 30%; background-color: #d05454;"| |- |Begnins || style="width: 30%; background-color: #d05454;"| |- |Beinwil (Freiamt) || style="width: 30%; background-color: #d05454;"| |- |Beinwil am See || style="width: 30%; background-color: #d05454;"| |- |Beinwil SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Belalp || style="width: 30%; background-color: #d05454;"| |- |Belfaux || style="width: 30%; background-color: #d05454;"| |- |Bellach || style="width: 30%; background-color: #99FF99;"|Argus |- |Bellelay || style="width: 30%; background-color: #d05454;"| |- |Bellerive VD || style="width: 30%; background-color: #d05454;"| |- |Bellevue || style="width: 30%; background-color: #d05454;"| |- |Bellikon || style="width: 30%; background-color: #d05454;"| |- |Bellinzona || style="width: 30%; background-color: #d05454;"| |- |Bellmund || style="width: 30%; background-color: #d05454;"| |- |Bellwald || style="width: 30%; background-color: #d05454;"| |- |Belmont-sur-Lausanne || style="width: 30%; background-color: #d05454;"| |- |Belmont-sur-Yverdon || style="width: 30%; background-color: #d05454;"| |- |Belp || style="width: 30%; background-color: #d05454;"| |- |Belpberg || style="width: 30%; background-color: #d05454;"| |- |Belprahon || style="width: 30%; background-color: #d05454;"| |- |Benglen || style="width: 30%; background-color: #d05454;"| |- |Benken SG || style="width: 30%; background-color: #d05454;"| |- |Benken ZH || style="width: 30%; background-color: #d05454;"| |- |Bennau || style="width: 30%; background-color: #d05454;"| |- |Bennwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Benzenschwil || style="width: 30%; background-color: #d05454;"| |- |Bercher || style="width: 30%; background-color: #d05454;"| |- |Berg (Dägerlen) || style="width: 30%; background-color: #d05454;"| |- |Berg am Irchel || style="width: 30%; background-color: #d05454;"| |- |Berg SG || style="width: 30%; background-color: #d05454;"| |- |Berg TG || style="width: 30%; background-color: #d05454;"| |- |Bergdietikon || style="width: 30%; background-color: #d05454;"| |- |Bergün/Bravuogn || style="width: 30%; background-color: #d05454;"| |- |Berikon || style="width: 30%; background-color: #99FF99;"|Argus |- |Beringen || style="width: 30%; background-color: #d05454;"| |- |Berken || style="width: 30%; background-color: #d05454;"| |- |Berlens || style="width: 30%; background-color: #d05454;"| |- |Berlingen || style="width: 30%; background-color: #d05454;"| |- |Bern || style="width: 30%; background-color: #99FF99;"|Argus |- |Berneck || style="width: 30%; background-color: #d05454;"| |- |Bernex || style="width: 30%; background-color: #d05454;"| |- |Bernhardzell || style="width: 30%; background-color: #d05454;"| |- |Berolle || style="width: 30%; background-color: #d05454;"| |- |Beromünster || style="width: 30%; background-color: #d05454;"| |- |Berschis || style="width: 30%; background-color: #d05454;"| |- |Bertschikon (Gossau ZH) || style="width: 30%; background-color: #d05454;"| |- |Berzona || style="width: 30%; background-color: #d05454;"| |- |Besazio || style="width: 30%; background-color: #d05454;"| |- |Besenbüren || style="width: 30%; background-color: #d05454;"| |- |Besencens || style="width: 30%; background-color: #d05454;"| |- |Betschwanden || style="width: 30%; background-color: #d05454;"| |- |Betten || style="width: 30%; background-color: #d05454;"| |- |Bettenhausen || style="width: 30%; background-color: #d05454;"| |- |Bettens || style="width: 30%; background-color: #d05454;"| |- |Bettingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Bettlach || style="width: 30%; background-color: #99FF99;"|Argus |- |Bettmeralp || style="width: 30%; background-color: #d05454;"| |- |Bettwiesen || style="width: 30%; background-color: #d05454;"| |- |Bettwil || style="width: 30%; background-color: #d05454;"| |- |Beurnevésin || style="width: 30%; background-color: #d05454;"| |- |Beuson (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Bevaix || style="width: 30%; background-color: #d05454;"| |- |Bever || style="width: 30%; background-color: #d05454;"| |- |Bévilard || style="width: 30%; background-color: #d05454;"| |- |Bex || style="width: 30%; background-color: #d05454;"| |- |Biasca || style="width: 30%; background-color: #d05454;"| |- |Biberist || style="width: 30%; background-color: #d05454;"| |- |Bibern SH || style="width: 30%; background-color: #d05454;"| |- |Bibern SO || style="width: 30%; background-color: #d05454;"| |- |Biberstein || style="width: 30%; background-color: #99FF99;"|Argus |- |Bichelsee || style="width: 30%; background-color: #d05454;"| |- |Bichwil || style="width: 30%; background-color: #d05454;"| |- |Bidogno || style="width: 30%; background-color: #d05454;"| |- |Biel VS || style="width: 30%; background-color: #d05454;"| |- |Biel-Benken BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Biel/Bienne || style="width: 30%; background-color: #d05454;"| |- |Biembach || style="width: 30%; background-color: #d05454;"| |- |Bière || style="width: 30%; background-color: #d05454;"| |- |Bieudron (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Biezwil || style="width: 30%; background-color: #d05454;"| |- |Bigenthal || style="width: 30%; background-color: #d05454;"| |- |Biglen || style="width: 30%; background-color: #d05454;"| |- |Bignasco || style="width: 30%; background-color: #d05454;"| |- |Bigorio || style="width: 30%; background-color: #d05454;"| |- |Billens || style="width: 30%; background-color: #d05454;"| |- |Bilten || style="width: 30%; background-color: #d05454;"| |- |Binn || style="width: 30%; background-color: #d05454;"| |- |Binningen || style="width: 30%; background-color: #99FF99;"|Argus |- |Binz || style="width: 30%; background-color: #d05454;"| |- |Bioggio || style="width: 30%; background-color: #d05454;"| |- |Biogno-Beride || style="width: 30%; background-color: #d05454;"| |- |Bioley-de-Brignon || style="width: 30%; background-color: #d05454;"| |- |Bioley-Magnoux || style="width: 30%; background-color: #d05454;"| |- |Bioley-Orjulaz || style="width: 30%; background-color: #d05454;"| |- |Bionnens || style="width: 30%; background-color: #d05454;"| |- |Birgisch || style="width: 30%; background-color: #d05454;"| |- |Birmensdorf ZH || style="width: 30%; background-color: #99FF99;"|Argus |- |Birmenstorf AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Bironico || style="width: 30%; background-color: #d05454;"| |- |Birr || style="width: 30%; background-color: #99FF99;"|Argus |- |Birrhard || style="width: 30%; background-color: #99FF99;"|Argus |- |Birrwil || style="width: 30%; background-color: #d05454;"| |- |Birsfelden || style="width: 30%; background-color: #99FF99;"|Argus |- |Birwinken || style="width: 30%; background-color: #d05454;"| |- |Bischofszell || style="width: 30%; background-color: #d05454;"| |- |Bisisthal || style="width: 30%; background-color: #d05454;"| |- |Bissegg || style="width: 30%; background-color: #d05454;"| |- |Bissone || style="width: 30%; background-color: #d05454;"| |- |Bister || style="width: 30%; background-color: #d05454;"| |- |Bitsch || style="width: 30%; background-color: #d05454;"| |- |Bivio || style="width: 30%; background-color: #d05454;"| |- |Blankenburg || style="width: 30%; background-color: #d05454;"| |- |Blatten (Lötschen) || style="width: 30%; background-color: #d05454;"| |- |Blatten b. Naters || style="width: 30%; background-color: #d05454;"| |- |Blauen || style="width: 30%; background-color: #99FF99;"|Argus |- |Blausee-Mitholz || style="width: 30%; background-color: #d05454;"| |- |Bleienbach || style="width: 30%; background-color: #d05454;"| |- |Bleiken || style="width: 30%; background-color: #d05454;"| |- |Blessens || style="width: 30%; background-color: #d05454;"| |- |Blignoud (Ayent) || style="width: 30%; background-color: #d05454;"| |- |Blitzingen || style="width: 30%; background-color: #d05454;"| |- |Blonay || style="width: 30%; background-color: #d05454;"| |- |Blumenstein || style="width: 30%; background-color: #d05454;"| |- |Böbikon || style="width: 30%; background-color: #99FF99;"|Argus |- |Böckten || style="width: 30%; background-color: #99FF99;"|Argus |- |Bodio TI || style="width: 30%; background-color: #d05454;"| |- |Boécourt || style="width: 30%; background-color: #d05454;"| |- |Bofflens || style="width: 30%; background-color: #d05454;"| |- |Bogis-Bossey || style="width: 30%; background-color: #d05454;"| |- |Bogno || style="width: 30%; background-color: #d05454;"| |- |Bôle || style="width: 30%; background-color: #d05454;"| |- |Bolken || style="width: 30%; background-color: #d05454;"| |- |Boll || style="width: 30%; background-color: #d05454;"| |- |Bolligen || style="width: 30%; background-color: #d05454;"| |- |Bollingen || style="width: 30%; background-color: #d05454;"| |- |Bollion || style="width: 30%; background-color: #d05454;"| |- |Bollodingen || style="width: 30%; background-color: #d05454;"| |- |Boltigen || style="width: 30%; background-color: #d05454;"| |- |Bombinasco || style="width: 30%; background-color: #d05454;"| |- |Bonaduz || style="width: 30%; background-color: #d05454;"| |- |Bonau || style="width: 30%; background-color: #d05454;"| |- |Boncourt || style="width: 30%; background-color: #d05454;"| |- |Bonfol || style="width: 30%; background-color: #d05454;"| |- |Bönigen b. Interlaken || style="width: 30%; background-color: #d05454;"| |- |Boningen || style="width: 30%; background-color: #d05454;"| |- |Boniswil || style="width: 30%; background-color: #d05454;"| |- |Bonnefontaine || style="width: 30%; background-color: #d05454;"| |- |Bonstetten || style="width: 30%; background-color: #99FF99;"|Argus |- |Bonvillars || style="width: 30%; background-color: #d05454;"| |- |Boppelsen || style="width: 30%; background-color: #99FF99;"|Argus |- |Borex || style="width: 30%; background-color: #d05454;"| |- |Borgnone || style="width: 30%; background-color: #d05454;"| |- |Borgonovo || style="width: 30%; background-color: #d05454;"| |- |Bosco Luganese || style="width: 30%; background-color: #d05454;"| |- |Bosco/Gurin || style="width: 30%; background-color: #d05454;"| |- |Bösingen || style="width: 30%; background-color: #d05454;"| |- |Bossonnens || style="width: 30%; background-color: #d05454;"| |- |Boswil || style="width: 30%; background-color: #d05454;"| |- |Bottens || style="width: 30%; background-color: #d05454;"| |- |Bottenwil || style="width: 30%; background-color: #d05454;"| |- |Botterens || style="width: 30%; background-color: #d05454;"| |- |Bottighofen || style="width: 30%; background-color: #d05454;"| |- |Bottmingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Böttstein || style="width: 30%; background-color: #99FF99;"|Argus |- |Botyre (Ayent) || style="width: 30%; background-color: #d05454;"| |- |Boudevilliers || style="width: 30%; background-color: #d05454;"| |- |Boudry || style="width: 30%; background-color: #d05454;"| |- |Bougy-Villars || style="width: 30%; background-color: #d05454;"| |- |Boulens || style="width: 30%; background-color: #d05454;"| |- |Bouloz || style="width: 30%; background-color: #d05454;"| |- |Bourg-St-Pierre || style="width: 30%; background-color: #d05454;"| |- |Bourguillon || style="width: 30%; background-color: #d05454;"| |- |Bournens || style="width: 30%; background-color: #d05454;"| |- |Bourrignon || style="width: 30%; background-color: #d05454;"| |- |Boussens || style="width: 30%; background-color: #d05454;"| |- |Bouveret || style="width: 30%; background-color: #d05454;"| |- |Boveresse || style="width: 30%; background-color: #d05454;"| |- |Bovernier || style="width: 30%; background-color: #d05454;"| |- |Bowil || style="width: 30%; background-color: #d05454;"| |- |Bözberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Bözen || style="width: 30%; background-color: #99FF99;"|Argus |- |Braggio || style="width: 30%; background-color: #d05454;"| |- |Brail || style="width: 30%; background-color: #d05454;"| |- |Bramboden || style="width: 30%; background-color: #d05454;"| |- |Bramois || style="width: 30%; background-color: #d05454;"| |- |Bratsch || style="width: 30%; background-color: #d05454;"| |- |Braunau || style="width: 30%; background-color: #d05454;"| |- |Braunwald || style="width: 30%; background-color: #d05454;"| |- |Brè sopra Lugano || style="width: 30%; background-color: #d05454;"| |- |Breganzona || style="width: 30%; background-color: #d05454;"| |- |Breil/Brigels || style="width: 30%; background-color: #d05454;"| |- |Breitenbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Bremblens || style="width: 30%; background-color: #d05454;"| |- |Bremgarten AG || style="width: 30%; background-color: #d05454;"| |- |Bremgarten b. Bern || style="width: 30%; background-color: #d05454;"| |- |Brenles || style="width: 30%; background-color: #d05454;"| |- |Breno || style="width: 30%; background-color: #d05454;"| |- |Brent || style="width: 30%; background-color: #d05454;"| |- |Brenzikofen || style="width: 30%; background-color: #d05454;"| |- |Bressaucourt || style="width: 30%; background-color: #d05454;"| |- |Bretaye || style="width: 30%; background-color: #d05454;"| |- |Bretigny-sur-Morrens || style="width: 30%; background-color: #d05454;"| |- |Bretonnières || style="width: 30%; background-color: #d05454;"| |- |Bretzwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Brienz BE || style="width: 30%; background-color: #d05454;"| |- |Brienz/Brinzauls GR || style="width: 30%; background-color: #d05454;"| |- |Brienzwiler || style="width: 30%; background-color: #d05454;"| |- |Brig || style="width: 30%; background-color: #d05454;"| |- |Brigerbad || style="width: 30%; background-color: #d05454;"| |- |Brignon (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Brione (Verzasca) || style="width: 30%; background-color: #d05454;"| |- |Brione sopra Minusio || style="width: 30%; background-color: #d05454;"| |- |Brislach || style="width: 30%; background-color: #99FF99;"|Argus |- |Brissago || style="width: 30%; background-color: #d05454;"| |- |Bristen || style="width: 30%; background-color: #d05454;"| |- |Brittern || style="width: 30%; background-color: #d05454;"| |- |Brittnau || style="width: 30%; background-color: #d05454;"| |- |Broc || style="width: 30%; background-color: #d05454;"| |- |Broglio || style="width: 30%; background-color: #d05454;"| |- |Bronschhofen || style="width: 30%; background-color: #d05454;"| |- |Brontallo || style="width: 30%; background-color: #d05454;"| |- |Brot-Dessous || style="width: 30%; background-color: #d05454;"| |- |Brot-Dessus || style="width: 30%; background-color: #d05454;"| |- |Brot-Plamboz || style="width: 30%; background-color: #d05454;"| |- |Bruderholz || style="width: 30%; background-color: #99FF99;"|Argus |- |Brugg AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Brügg BE || style="width: 30%; background-color: #d05454;"| |- |Brügglen || style="width: 30%; background-color: #d05454;"| |- |Brülisau || style="width: 30%; background-color: #d05454;"| |- |Brunegg || style="width: 30%; background-color: #99FF99;"|Argus |- |Brünig || style="width: 30%; background-color: #d05454;"| |- |Brünisried || style="width: 30%; background-color: #d05454;"| |- |Brunnadern || style="width: 30%; background-color: #d05454;"| |- |Brunnen || style="width: 30%; background-color: #d05454;"| |- |Brunnenthal || style="width: 30%; background-color: #d05454;"| |- |Brusino Arsizio || style="width: 30%; background-color: #d05454;"| |- |Brusio || style="width: 30%; background-color: #d05454;"| |- |Bruson || style="width: 30%; background-color: #d05454;"| |- |Brüttelen || style="width: 30%; background-color: #d05454;"| |- |Brütten || style="width: 30%; background-color: #d05454;"| |- |Brüttisellen || style="width: 30%; background-color: #d05454;"| |- |Bruzella || style="width: 30%; background-color: #d05454;"| |- |Bubendorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Bubikon || style="width: 30%; background-color: #d05454;"| |- |Buch am Irchel || style="width: 30%; background-color: #d05454;"| |- |Buch b. Frauenfeld || style="width: 30%; background-color: #d05454;"| |- |Buch b. Kümmertshausen || style="width: 30%; background-color: #d05454;"| |- |Buch b. Märwil || style="width: 30%; background-color: #d05454;"| |- |Buch SH || style="width: 30%; background-color: #d05454;"| |- |Buchackern || style="width: 30%; background-color: #d05454;"| |- |Buchberg || style="width: 30%; background-color: #d05454;"| |- |Buchen || style="width: 30%; background-color: #d05454;"| |- |Buchen BE || style="width: 30%; background-color: #d05454;"| |- |Buchillon || style="width: 30%; background-color: #d05454;"| |- |Buchrain || style="width: 30%; background-color: #d05454;"| |- |Buchs AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Buchs LU || style="width: 30%; background-color: #d05454;"| |- |Buchs SG || style="width: 30%; background-color: #d05454;"| |- |Buchs ZH || style="width: 30%; background-color: #d05454;"| |- |Büchslen || style="width: 30%; background-color: #d05454;"| |- |Buckten || style="width: 30%; background-color: #d05454;"| |- |Büetigen || style="width: 30%; background-color: #d05454;"| |- |Bühl BE || style="width: 30%; background-color: #d05454;"| |- |Bühler || style="width: 30%; background-color: #d05454;"| |- |Buhwil || style="width: 30%; background-color: #d05454;"| |- |Buix || style="width: 30%; background-color: #d05454;"| |- |Bülach || style="width: 30%; background-color: #d05454;"| |- |Bulle || style="width: 30%; background-color: #d05454;"| |- |Bullet || style="width: 30%; background-color: #d05454;"| |- |Bünzen || style="width: 30%; background-color: #d05454;"| |- |Buochs || style="width: 30%; background-color: #d05454;"| |- |Buonas || style="width: 30%; background-color: #d05454;"| |- |Bürchen || style="width: 30%; background-color: #d05454;"| |- |Bure || style="width: 30%; background-color: #d05454;"| |- |Büren an der Aare || style="width: 30%; background-color: #d05454;"| |- |Büren NW || style="width: 30%; background-color: #d05454;"| |- |Büren SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Büren zum Hof || style="width: 30%; background-color: #d05454;"| |- |Burg AG || style="width: 30%; background-color: #d05454;"| |- |Burg im Leimental || style="width: 30%; background-color: #d05454;"| |- |Burgäschi || style="width: 30%; background-color: #d05454;"| |- |Burgdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Bürgenstock || style="width: 30%; background-color: #d05454;"| |- |Burgistein || style="width: 30%; background-color: #d05454;"| |- |Burglauenen || style="width: 30%; background-color: #d05454;"| |- |Bürglen OW || style="width: 30%; background-color: #d05454;"| |- |Bürglen TG || style="width: 30%; background-color: #d05454;"| |- |Bürglen UR || style="width: 30%; background-color: #d05454;"| |- |Büron || style="width: 30%; background-color: #d05454;"| |- |Bursinel || style="width: 30%; background-color: #d05454;"| |- |Bursins || style="width: 30%; background-color: #d05454;"| |- |Burtigny || style="width: 30%; background-color: #d05454;"| |- |Buseno || style="width: 30%; background-color: #d05454;"| |- |Büsserach || style="width: 30%; background-color: #99FF99;"|Argus |- |Bussigny-près-Lausanne || style="width: 30%; background-color: #d05454;"| |- |Bussigny-sur-Oron || style="width: 30%; background-color: #d05454;"| |- |Bussnang || style="width: 30%; background-color: #d05454;"| |- |Busswil b. Büren || style="width: 30%; background-color: #d05454;"| |- |Busswil b. Melchnau || style="width: 30%; background-color: #d05454;"| |- |Busswil TG || style="width: 30%; background-color: #d05454;"| |- |Bussy FR || style="width: 30%; background-color: #d05454;"| |- |Bussy-Chardonney || style="width: 30%; background-color: #d05454;"| |- |Bussy-sur-Moudon || style="width: 30%; background-color: #d05454;"| |- |Bütschwil || style="width: 30%; background-color: #d05454;"| |- |Büttenhardt || style="width: 30%; background-color: #d05454;"| |- |Buttes || style="width: 30%; background-color: #d05454;"| |- |Büttikon AG || style="width: 30%; background-color: #d05454;"| |- |Buttikon SZ || style="width: 30%; background-color: #d05454;"| |- |Buttisholz || style="width: 30%; background-color: #d05454;"| |- |Buttwil || style="width: 30%; background-color: #d05454;"| |- |Bützberg || style="width: 30%; background-color: #d05454;"| |- |Buus || style="width: 30%; background-color: #99FF99;"|Argus |- |Cabbio || style="width: 30%; background-color: #d05454;"| |- |Cademario || style="width: 30%; background-color: #d05454;"| |- |Cadempino || style="width: 30%; background-color: #d05454;"| |- |Cadenazzo || style="width: 30%; background-color: #d05454;"| |- |Cadro || style="width: 30%; background-color: #d05454;"| |- |Cagiallo || style="width: 30%; background-color: #d05454;"| |- |Calfreisen || style="width: 30%; background-color: #d05454;"| |- |Calonico || style="width: 30%; background-color: #d05454;"| |- |Calpiogna || style="width: 30%; background-color: #d05454;"| |- |Cama || style="width: 30%; background-color: #d05454;"| |- |Camedo || style="width: 30%; background-color: #d05454;"| |- |Camignolo || style="width: 30%; background-color: #d05454;"| |- |Camischolas || style="width: 30%; background-color: #d05454;"| |- |Camorino || style="width: 30%; background-color: #d05454;"| |- |Campascio || style="width: 30%; background-color: #d05454;"| |- |Campello || style="width: 30%; background-color: #d05454;"| |- |Camperio || style="width: 30%; background-color: #d05454;"| |- |Campo (Blenio) || style="width: 30%; background-color: #d05454;"| |- |Campo (VM) || style="width: 30%; background-color: #d05454;"| |- |Campocologno || style="width: 30%; background-color: #d05454;"| |- |Campsut-Cröt || style="width: 30%; background-color: #d05454;"| |- |Camuns || style="width: 30%; background-color: #d05454;"| |- |Caneggio || style="width: 30%; background-color: #d05454;"| |- |Canobbio || style="width: 30%; background-color: #d05454;"| |- |Capolago || style="width: 30%; background-color: #d05454;"| |- |Carabbia || style="width: 30%; background-color: #d05454;"| |- |Carabietta || style="width: 30%; background-color: #d05454;"| |- |Carena || style="width: 30%; background-color: #d05454;"| |- |Carì || style="width: 30%; background-color: #d05454;"| |- |Carona || style="width: 30%; background-color: #d05454;"| |- |Carouge GE || style="width: 30%; background-color: #d05454;"| |- |Carrera || style="width: 30%; background-color: #d05454;"| |- |Carrouge VD || style="width: 30%; background-color: #d05454;"| |- |Cartigny || style="width: 30%; background-color: #d05454;"| |- |Casaccia || style="width: 30%; background-color: #d05454;"| |- |Casima || style="width: 30%; background-color: #d05454;"| |- |Caslano || style="width: 30%; background-color: #d05454;"| |- |Cassina d‘Agno || style="width: 30%; background-color: #d05454;"| |- |Castagnola || style="width: 30%; background-color: #d05454;"| |- |Castaneda || style="width: 30%; background-color: #d05454;"| |- |Castasegna || style="width: 30%; background-color: #d05454;"| |- |Castel San Pietro || style="width: 30%; background-color: #d05454;"| |- |Castelrotto || style="width: 30%; background-color: #d05454;"| |- |Castiel || style="width: 30%; background-color: #d05454;"| |- |Castione || style="width: 30%; background-color: #d05454;"| |- |Castrisch || style="width: 30%; background-color: #d05454;"| |- |Castro || style="width: 30%; background-color: #d05454;"| |- |Cauco || style="width: 30%; background-color: #d05454;"| |- |Caux || style="width: 30%; background-color: #d05454;"| |- |Cavagnago || style="width: 30%; background-color: #d05454;"| |- |Cavardiras || style="width: 30%; background-color: #d05454;"| |- |Cavergno || style="width: 30%; background-color: #d05454;"| |- |Caviano || style="width: 30%; background-color: #d05454;"| |- |Cavigliano || style="width: 30%; background-color: #d05454;"| |- |Cazis || style="width: 30%; background-color: #d05454;"| |- |Celerina/Schlarigna || style="width: 30%; background-color: #d05454;"| |- |Céligny || style="width: 30%; background-color: #d05454;"| |- |Cerentino || style="width: 30%; background-color: #d05454;"| |- |Cerneux-Péquignot || style="width: 30%; background-color: #d05454;"| |- |Cerniat FR || style="width: 30%; background-color: #d05454;"| |- |Cerniaz VD || style="width: 30%; background-color: #d05454;"| |- |Cernier || style="width: 30%; background-color: #d05454;"| |- |Certara || style="width: 30%; background-color: #d05454;"| |- |Cevio || style="width: 30%; background-color: #d05454;"| |- |Châbles FR || style="width: 30%; background-color: #d05454;"| |- |Chabrey || style="width: 30%; background-color: #d05454;"| |- |Chailly-Montreux || style="width: 30%; background-color: #d05454;"| |- |Chalais || style="width: 30%; background-color: #d05454;"| |- |Cham || style="width: 30%; background-color: #d05454;"| |- |Chambésy || style="width: 30%; background-color: #d05454;"| |- |Chamblon || style="width: 30%; background-color: #d05454;"| |- |Chambrelien || style="width: 30%; background-color: #d05454;"| |- |Chamby || style="width: 30%; background-color: #d05454;"| |- |Chamoille || style="width: 30%; background-color: #d05454;"| |- |Chamoson || style="width: 30%; background-color: #d05454;"| |- |Champ-du-Moulin || style="width: 30%; background-color: #d05454;"| |- |Champagne || style="width: 30%; background-color: #d05454;"| |- |Champéry || style="width: 30%; background-color: #d05454;"| |- |Champex-Lac || style="width: 30%; background-color: #d05454;"| |- |Champfèr || style="width: 30%; background-color: #d05454;"| |- |Champlan || style="width: 30%; background-color: #d05454;"| |- |Champoussin || style="width: 30%; background-color: #d05454;"| |- |Champoz || style="width: 30%; background-color: #d05454;"| |- |Champsec || style="width: 30%; background-color: #d05454;"| |- |Champtauroz || style="width: 30%; background-color: #d05454;"| |- |Champvent || style="width: 30%; background-color: #d05454;"| |- |Champzabé || style="width: 30%; background-color: #d05454;"| |- |Chancy || style="width: 30%; background-color: #d05454;"| |- |Chandolin || style="width: 30%; background-color: #d05454;"| |- |Chandolin-Savièse || style="width: 30%; background-color: #d05454;"| |- |Chandon || style="width: 30%; background-color: #d05454;"| |- |Chandonne (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Chanéaz || style="width: 30%; background-color: #d05454;"| |- |Chapelle (Broye) || style="width: 30%; background-color: #d05454;"| |- |Chapelle (Glâne) || style="width: 30%; background-color: #d05454;"| |- |Chapelle-sur-Moudon || style="width: 30%; background-color: #d05454;"| |- |Chardonne || style="width: 30%; background-color: #d05454;"| |- |Charmey (Gruyère) || style="width: 30%; background-color: #d05454;"| |- |Charmoille || style="width: 30%; background-color: #d05454;"| |- |Charrat || style="width: 30%; background-color: #d05454;"| |- |Château-d‘Oex || style="width: 30%; background-color: #d05454;"| |- |Châtel-St-Denis || style="width: 30%; background-color: #d05454;"| |- |Châtel-sur-Montsalvens || style="width: 30%; background-color: #d05454;"| |- |Châtelaine || style="width: 30%; background-color: #d05454;"| |- |Châtelat || style="width: 30%; background-color: #d05454;"| |- |Châtillens || style="width: 30%; background-color: #d05454;"| |- |Châtillon FR || style="width: 30%; background-color: #d05454;"| |- |Châtillon JU || style="width: 30%; background-color: #d05454;"| |- |Châtonnaye || style="width: 30%; background-color: #99FF99;"|Argus |- |Chaumont || style="width: 30%; background-color: #d05454;"| |- |Chavannes-de-Bogis || style="width: 30%; background-color: #d05454;"| |- |Chavannes-des-Bois || style="width: 30%; background-color: #d05454;"| |- |Chavannes-le-Chêne || style="width: 30%; background-color: #d05454;"| |- |Chavannes-le-Veyron || style="width: 30%; background-color: #d05454;"| |- |Chavannes-les-Forts || style="width: 30%; background-color: #d05454;"| |- |Chavannes-près-Renens || style="width: 30%; background-color: #d05454;"| |- |Chavannes-sous-Orsonnens || style="width: 30%; background-color: #d05454;"| |- |Chavannes-sur-Moudon || style="width: 30%; background-color: #d05454;"| |- |Chavornay || style="width: 30%; background-color: #d05454;"| |- |Cheiry || style="width: 30%; background-color: #d05454;"| |- |Chemin || style="width: 30%; background-color: #d05454;"| |- |Chenaux || style="width: 30%; background-color: #d05454;"| |- |Chêne-Bougeries || style="width: 30%; background-color: #d05454;"| |- |Chêne-Bourg || style="width: 30%; background-color: #d05454;"| |- |Chêne-Pâquier || style="width: 30%; background-color: #d05454;"| |- |Chénens || style="width: 30%; background-color: #99FF99;"|Argus |- |Chermignon || style="width: 30%; background-color: #d05454;"| |- |Chermignon-d'en-Bas || style="width: 30%; background-color: #d05454;"| |- |Chernex || style="width: 30%; background-color: #d05454;"| |- |Chesalles-sur-Moudon || style="width: 30%; background-color: #d05454;"| |- |Chesalles-sur-Oron || style="width: 30%; background-color: #d05454;"| |- |Cheseaux || style="width: 30%; background-color: #d05454;"| |- |Cheseaux-sur-Lausanne || style="width: 30%; background-color: #d05454;"| |- |Chéserex || style="width: 30%; background-color: #d05454;"| |- |Chesières || style="width: 30%; background-color: #d05454;"| |- |Chésopelloz || style="width: 30%; background-color: #d05454;"| |- |Chessel || style="width: 30%; background-color: #d05454;"| |- |Chevenez || style="width: 30%; background-color: #d05454;"| |- |Chevilly || style="width: 30%; background-color: #d05454;"| |- |Chevroux || style="width: 30%; background-color: #d05454;"| |- |Chexbres || style="width: 30%; background-color: #d05454;"| |- |Cheyres || style="width: 30%; background-color: #d05454;"| |- |Chez Petit (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Chez-le-Bart || style="width: 30%; background-color: #d05454;"| |- |Chézard-St-Martin || style="width: 30%; background-color: #d05454;"| |- |Chiasso || style="width: 30%; background-color: #d05454;"| |- |Chiggiogna || style="width: 30%; background-color: #d05454;"| |- |Chigny || style="width: 30%; background-color: #d05454;"| |- |Chippis || style="width: 30%; background-color: #d05454;"| |- |Chironico || style="width: 30%; background-color: #d05454;"| |- |Choëx || style="width: 30%; background-color: #d05454;"| |- |Choindez || style="width: 30%; background-color: #d05454;"| |- |Choulex || style="width: 30%; background-color: #d05454;"| |- |Chur || style="width: 30%; background-color: #d05454;"| |- |Churwalden || style="width: 30%; background-color: #d05454;"| |- |Cimadera || style="width: 30%; background-color: #d05454;"| |- |Cimalmotto || style="width: 30%; background-color: #d05454;"| |- |Cimo || style="width: 30%; background-color: #d05454;"| |- |Cinuos-chel || style="width: 30%; background-color: #d05454;"| |- |Clarens || style="width: 30%; background-color: #d05454;"| |- |Clarmont || style="width: 30%; background-color: #d05454;"| |- |Claro || style="width: 30%; background-color: #d05454;"| |- |Clavaleyres || style="width: 30%; background-color: #d05454;"| |- |Clèbes (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Clugin || style="width: 30%; background-color: #d05454;"| |- |Coeuve || style="width: 30%; background-color: #d05454;"| |- |Coffrane || style="width: 30%; background-color: #d05454;"| |- |Coglio || style="width: 30%; background-color: #d05454;"| |- |Coinsins || style="width: 30%; background-color: #d05454;"| |- |Cointrin || style="width: 30%; background-color: #d05454;"| |- |Coldrerio || style="width: 30%; background-color: #d05454;"| |- |Colla || style="width: 30%; background-color: #d05454;"| |- |Collex || style="width: 30%; background-color: #d05454;"| |- |Collombey || style="width: 30%; background-color: #d05454;"| |- |Collonge-Bellerive || style="width: 30%; background-color: #d05454;"| |- |Collonges || style="width: 30%; background-color: #d05454;"| |- |Cologny || style="width: 30%; background-color: #d05454;"| |- |Colombier NE || style="width: 30%; background-color: #d05454;"| |- |Colombier VD || style="width: 30%; background-color: #d05454;"| |- |Comano || style="width: 30%; background-color: #d05454;"| |- |Combremont-le-Grand || style="width: 30%; background-color: #d05454;"| |- |Combremont-le-Petit || style="width: 30%; background-color: #d05454;"| |- |Commugny || style="width: 30%; background-color: #d05454;"| |- |Comologno || style="width: 30%; background-color: #d05454;"| |- |Conches || style="width: 30%; background-color: #d05454;"| |- |Concise || style="width: 30%; background-color: #d05454;"| |- |Condémines (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Confignon || style="width: 30%; background-color: #d05454;"| |- |Constantine || style="width: 30%; background-color: #d05454;"| |- |Conters || style="width: 30%; background-color: #d05454;"| |- |Conthey || style="width: 30%; background-color: #d05454;"| |- |Contone || style="width: 30%; background-color: #d05454;"| |- |Contra || style="width: 30%; background-color: #d05454;"| |- |Coppet || style="width: 30%; background-color: #d05454;"| |- |Corban || style="width: 30%; background-color: #d05454;"| |- |Corbeyrier || style="width: 30%; background-color: #d05454;"| |- |Corbières || style="width: 30%; background-color: #d05454;"| |- |Corcelles BE || style="width: 30%; background-color: #d05454;"| |- |Corcelles NE || style="width: 30%; background-color: #d05454;"| |- |Corcelles-le-Jorat || style="width: 30%; background-color: #d05454;"| |- |Corcelles-près-Concise || style="width: 30%; background-color: #d05454;"| |- |Corcelles-près-Payerne || style="width: 30%; background-color: #d05454;"| |- |Corcelles-sur-Chavornay || style="width: 30%; background-color: #d05454;"| |- |Cordast || style="width: 30%; background-color: #d05454;"| |- |Corgémont || style="width: 30%; background-color: #d05454;"| |- |Corin-de-la-Crête || style="width: 30%; background-color: #d05454;"| |- |Corippo || style="width: 30%; background-color: #d05454;"| |- |Corjolens || style="width: 30%; background-color: #d05454;"| |- |Cormagens || style="width: 30%; background-color: #d05454;"| |- |Cormérod || style="width: 30%; background-color: #d05454;"| |- |Corminboeuf || style="width: 30%; background-color: #d05454;"| |- |Cormondrèche || style="width: 30%; background-color: #d05454;"| |- |Cormoret || style="width: 30%; background-color: #d05454;"| |- |Cornaux NE || style="width: 30%; background-color: #d05454;"| |- |Cornol || style="width: 30%; background-color: #d05454;"| |- |Corpataux || style="width: 30%; background-color: #d05454;"| |- |Corrençon || style="width: 30%; background-color: #d05454;"| |- |Correvon || style="width: 30%; background-color: #d05454;"| |- |Corseaux || style="width: 30%; background-color: #d05454;"| |- |Corserey || style="width: 30%; background-color: #d05454;"| |- |Corsier GE || style="width: 30%; background-color: #d05454;"| |- |Corsier-sur-Vevey || style="width: 30%; background-color: #d05454;"| |- |Cortaillod || style="width: 30%; background-color: #d05454;"| |- |Cortébert || style="width: 30%; background-color: #d05454;"| |- |Corteglia || style="width: 30%; background-color: #d05454;"| |- |Corticiasca || style="width: 30%; background-color: #d05454;"| |- |Corzoneso || style="width: 30%; background-color: #d05454;"| |- |Cossonay-Ville || style="width: 30%; background-color: #d05454;"| |- |Cottens FR || style="width: 30%; background-color: #99FF99;"|Argus |- |Cottens VD || style="width: 30%; background-color: #d05454;"| |- |Cotterd || style="width: 30%; background-color: #d05454;"| |- |Cotterg (Le Châble) || style="width: 30%; background-color: #d05454;"| |- |Courcelon || style="width: 30%; background-color: #d05454;"| |- |Courchapoix || style="width: 30%; background-color: #d05454;"| |- |Courchavon || style="width: 30%; background-color: #d05454;"| |- |Courfaivre || style="width: 30%; background-color: #d05454;"| |- |Courgenay || style="width: 30%; background-color: #d05454;"| |- |Courgevaux || style="width: 30%; background-color: #d05454;"| |- |Courlevon || style="width: 30%; background-color: #d05454;"| |- |Cournillens || style="width: 30%; background-color: #d05454;"| |- |Courrendlin || style="width: 30%; background-color: #d05454;"| |- |Courroux || style="width: 30%; background-color: #d05454;"| |- |Court || style="width: 30%; background-color: #d05454;"| |- |Courtaman || style="width: 30%; background-color: #d05454;"| |- |Courtedoux || style="width: 30%; background-color: #d05454;"| |- |Courtelary || style="width: 30%; background-color: #d05454;"| |- |Courtemaîche || style="width: 30%; background-color: #d05454;"| |- |Courtemautruy || style="width: 30%; background-color: #d05454;"| |- |Courtepin || style="width: 30%; background-color: #d05454;"| |- |Courtételle || style="width: 30%; background-color: #d05454;"| |- |Courtion || style="width: 30%; background-color: #d05454;"| |- |Cousset || style="width: 30%; background-color: #d05454;"| |- |Couvet || style="width: 30%; background-color: #d05454;"| |- |Cozzo || style="width: 30%; background-color: #d05454;"| |- |Crana || style="width: 30%; background-color: #d05454;"| |- |Crans-Montana || style="width: 30%; background-color: #d05454;"| |- |Crans-près-Céligny || style="width: 30%; background-color: #d05454;"| |- |Crassier || style="width: 30%; background-color: #d05454;"| |- |Cremin || style="width: 30%; background-color: #d05454;"| |- |Crémines || style="width: 30%; background-color: #d05454;"| |- |Cresciano || style="width: 30%; background-color: #d05454;"| |- |Cressier FR || style="width: 30%; background-color: #d05454;"| |- |Cressier NE || style="width: 30%; background-color: #d05454;"| |- |Cresta (Avers) || style="width: 30%; background-color: #d05454;"| |- |Crésuz || style="width: 30%; background-color: #d05454;"| |- |Crête-à-l‘Oeil || style="width: 30%; background-color: #d05454;"| |- |Cries (Vollèges) || style="width: 30%; background-color: #d05454;"| |- |Crissier || style="width: 30%; background-color: #d05454;"| |- |Cronay || style="width: 30%; background-color: #d05454;"| |- |Croy || style="width: 30%; background-color: #d05454;"| |- |Crusch || style="width: 30%; background-color: #d05454;"| |- |Cuarnens || style="width: 30%; background-color: #d05454;"| |- |Cuarny || style="width: 30%; background-color: #d05454;"| |- |Cudrefin || style="width: 30%; background-color: #d05454;"| |- |Cugnasco || style="width: 30%; background-color: #d05454;"| |- |Cugy FR || style="width: 30%; background-color: #d05454;"| |- |Cugy VD || style="width: 30%; background-color: #d05454;"| |- |Cully || style="width: 30%; background-color: #d05454;"| |- |Cumbel || style="width: 30%; background-color: #d05454;"| |- |Cumpadials || style="width: 30%; background-color: #d05454;"| |- |Cunter || style="width: 30%; background-color: #d05454;"| |- |Curaglia || style="width: 30%; background-color: #d05454;"| |- |Cureggia || style="width: 30%; background-color: #d05454;"| |- |Cureglia || style="width: 30%; background-color: #d05454;"| |- |Curio || style="width: 30%; background-color: #d05454;"| |- |Curtilles || style="width: 30%; background-color: #d05454;"| |- |Curtina || style="width: 30%; background-color: #d05454;"| |- |Dachsen || style="width: 30%; background-color: #d05454;"| |- |Dägerlen || style="width: 30%; background-color: #d05454;"| |- |Dagmersellen || style="width: 30%; background-color: #d05454;"| |- |Daillens || style="width: 30%; background-color: #d05454;"| |- |Daillon || style="width: 30%; background-color: #d05454;"| |- |Daiwil || style="width: 30%; background-color: #d05454;"| |- |Dalin || style="width: 30%; background-color: #d05454;"| |- |Dallenwil || style="width: 30%; background-color: #d05454;"| |- |Dällikon || style="width: 30%; background-color: #99FF99;"|Argus |- |Dalpe || style="width: 30%; background-color: #d05454;"| |- |Damphreux || style="width: 30%; background-color: #d05454;"| |- |Damvant || style="width: 30%; background-color: #d05454;"| |- |Dangio || style="width: 30%; background-color: #d05454;"| |- |Däniken SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Dänikon ZH || style="width: 30%; background-color: #99FF99;"|Argus |- |Danis || style="width: 30%; background-color: #d05454;"| |- |Dardagny || style="width: 30%; background-color: #d05454;"| |- |Dardin || style="width: 30%; background-color: #d05454;"| |- |Därligen || style="width: 30%; background-color: #d05454;"| |- |Därstetten || style="width: 30%; background-color: #d05454;"| |- |Dättlikon || style="width: 30%; background-color: #d05454;"| |- |Dättwil AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Davesco-Soragno || style="width: 30%; background-color: #d05454;"| |- |Davos Clavadel || style="width: 30%; background-color: #d05454;"| |- |Davos Dorf || style="width: 30%; background-color: #d05454;"| |- |Davos Frauenkirch || style="width: 30%; background-color: #d05454;"| |- |Davos Glaris || style="width: 30%; background-color: #d05454;"| |- |Davos Monstein || style="width: 30%; background-color: #d05454;"| |- |Davos Platz || style="width: 30%; background-color: #d05454;"| |- |Davos Wiesen || style="width: 30%; background-color: #d05454;"| |- |Davos Wolfgang || style="width: 30%; background-color: #d05454;"| |- |Degen || style="width: 30%; background-color: #d05454;"| |- |Degersheim || style="width: 30%; background-color: #d05454;"| |- |Deisswil b. Münchenbuchsee || style="width: 30%; background-color: #d05454;"| |- |Deitingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Delémont || style="width: 30%; background-color: #d05454;"| |- |Delley || style="width: 30%; background-color: #d05454;"| |- |Démoret || style="width: 30%; background-color: #d05454;"| |- |Denens || style="width: 30%; background-color: #d05454;"| |- |Denezy || style="width: 30%; background-color: #d05454;"| |- |Denges || style="width: 30%; background-color: #d05454;"| |- |Densbüren || style="width: 30%; background-color: #99FF99;"|Argus |- |Derendingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Detligen || style="width: 30%; background-color: #d05454;"| |- |Dettighofen || style="width: 30%; background-color: #d05454;"| |- |Develier || style="width: 30%; background-color: #d05454;"| |- |Dicken || style="width: 30%; background-color: #d05454;"| |- |Diegten || style="width: 30%; background-color: #99FF99;"|Argus |- |Dielsdorf || style="width: 30%; background-color: #d05454;"| |- |Diemerswil || style="width: 30%; background-color: #d05454;"| |- |Diemtigen || style="width: 30%; background-color: #d05454;"| |- |Diepflingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Diepoldsau || style="width: 30%; background-color: #d05454;"| |- |Dierikon || style="width: 30%; background-color: #d05454;"| |- |Diesbach GL || style="width: 30%; background-color: #d05454;"| |- |Diessbach b. Büren || style="width: 30%; background-color: #d05454;"| |- |Diesse || style="width: 30%; background-color: #d05454;"| |- |Diessenhofen || style="width: 30%; background-color: #d05454;"| |- |Dieterswil || style="width: 30%; background-color: #d05454;"| |- |Dietfurt || style="width: 30%; background-color: #d05454;"| |- |Dietikon || style="width: 30%; background-color: #99FF99;"|Argus |- |Dietlikon || style="width: 30%; background-color: #99FF99;"|Argus |- |Dietwil || style="width: 30%; background-color: #d05454;"| |- |Dinhard || style="width: 30%; background-color: #d05454;"| |- |Dino || style="width: 30%; background-color: #d05454;"| |- |Dintikon || style="width: 30%; background-color: #d05454;"| |- |Disentis/Mustér || style="width: 30%; background-color: #d05454;"| |- |Dittingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Dizy || style="width: 30%; background-color: #d05454;"| |- |Domat/Ems || style="width: 30%; background-color: #d05454;"| |- |Dombresson || style="width: 30%; background-color: #d05454;"| |- |Domdidier || style="width: 30%; background-color: #d05454;"| |- |Dommartin || style="width: 30%; background-color: #d05454;"| |- |Dompierre FR || style="width: 30%; background-color: #d05454;"| |- |Dompierre VD || style="width: 30%; background-color: #d05454;"| |- |Donat || style="width: 30%; background-color: #d05454;"| |- |Donatyre || style="width: 30%; background-color: #d05454;"| |- |Dongio || style="width: 30%; background-color: #d05454;"| |- |Donneloye || style="width: 30%; background-color: #d05454;"| |- |Donzhausen || style="width: 30%; background-color: #d05454;"| |- |Doppleschwand || style="width: 30%; background-color: #d05454;"| |- |Dorénaz || style="width: 30%; background-color: #d05454;"| |- |Dorf || style="width: 30%; background-color: #d05454;"| |- |Dörflingen || style="width: 30%; background-color: #d05454;"| |- |Dornach || style="width: 30%; background-color: #99FF99;"|Argus |- |Dotnacht || style="width: 30%; background-color: #d05454;"| |- |Dottikon || style="width: 30%; background-color: #d05454;"| |- |Döttingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Dotzigen || style="width: 30%; background-color: #d05454;"| |- |Dozwil || style="width: 30%; background-color: #d05454;"| |- |Dranse (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Dreien || style="width: 30%; background-color: #d05454;"| |- |Drône VS || style="width: 30%; background-color: #d05454;"| |- |Dübendorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Düdingen || style="width: 30%; background-color: #d05454;"| |- |Duggingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Dugny (Leytron) || style="width: 30%; background-color: #d05454;"| |- |Duillier || style="width: 30%; background-color: #d05454;"| |- |Dulliken || style="width: 30%; background-color: #99FF99;"|Argus |- |Dully || style="width: 30%; background-color: #d05454;"| |- |Dürnten || style="width: 30%; background-color: #d05454;"| |- |Dürrenäsch || style="width: 30%; background-color: #d05454;"| |- |Dürrenroth || style="width: 30%; background-color: #d05454;"| |- |Dussnang || style="width: 30%; background-color: #d05454;"| |- |Duvin || style="width: 30%; background-color: #d05454;"| |- |Ebersecken || style="width: 30%; background-color: #d05454;"| |- |Ebersol || style="width: 30%; background-color: #d05454;"| |- |Ebertswil || style="width: 30%; background-color: #d05454;"| |- |Ebikon || style="width: 30%; background-color: #d05454;"| |- |Ebmatingen || style="width: 30%; background-color: #d05454;"| |- |Ebnat-Kappel || style="width: 30%; background-color: #d05454;"| |- |Ebnet || style="width: 30%; background-color: #d05454;"| |- |Echallens || style="width: 30%; background-color: #d05454;"| |- |Echandens || style="width: 30%; background-color: #d05454;"| |- |Echarlens || style="width: 30%; background-color: #99FF99;"|Argus |- |Echichens || style="width: 30%; background-color: #d05454;"| |- |Eclagnens || style="width: 30%; background-color: #d05454;"| |- |Eclépens || style="width: 30%; background-color: #d05454;"| |- |Ecoteaux || style="width: 30%; background-color: #d05454;"| |- |Ecublens FR || style="width: 30%; background-color: #d05454;"| |- |Ecublens VD || style="width: 30%; background-color: #d05454;"| |- |Ecuvillens || style="width: 30%; background-color: #d05454;"| |- |Ederswiler || style="width: 30%; background-color: #99FF99;"|Argus |- |Edlibach || style="width: 30%; background-color: #d05454;"| |- |Effingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Effretikon || style="width: 30%; background-color: #d05454;"| |- |Egerkingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Egg (Flawil) || style="width: 30%; background-color: #d05454;"| |- |Egg b. Zürich || style="width: 30%; background-color: #d05454;"| |- |Egg SZ || style="width: 30%; background-color: #d05454;"| |- |Eggenwil || style="width: 30%; background-color: #d05454;"| |- |Eggerberg || style="width: 30%; background-color: #d05454;"| |- |Eggersriet || style="width: 30%; background-color: #d05454;"| |- |Eggethof || style="width: 30%; background-color: #d05454;"| |- |Eggiwil || style="width: 30%; background-color: #d05454;"| |- |Eglisau || style="width: 30%; background-color: #d05454;"| |- |Egliswil || style="width: 30%; background-color: #d05454;"| |- |Egnach || style="width: 30%; background-color: #d05454;"| |- |Egolzwil || style="width: 30%; background-color: #d05454;"| |- |Ehrendingen || style="width: 30%; background-color: #d05454;"| |- |Eich || style="width: 30%; background-color: #d05454;"| |- |Eichberg || style="width: 30%; background-color: #d05454;"| |- |Eigenthal || style="width: 30%; background-color: #d05454;"| |- |Eigergletscher || style="width: 30%; background-color: #d05454;"| |- |Eiken || style="width: 30%; background-color: #99FF99;"|Argus |- |Einigen || style="width: 30%; background-color: #d05454;"| |- |Einsiedeln || style="width: 30%; background-color: #d05454;"| |- |Eischoll || style="width: 30%; background-color: #d05454;"| |- |Eison (St.Martin) || style="width: 30%; background-color: #d05454;"| |- |Eisten || style="width: 30%; background-color: #d05454;"| |- |Elfingen || style="width: 30%; background-color: #d05454;"| |- |Elgg || style="width: 30%; background-color: #d05454;"| |- |Ellighausen || style="width: 30%; background-color: #d05454;"| |- |Ellikon am Rhein || style="width: 30%; background-color: #d05454;"| |- |Ellikon an der Thur || style="width: 30%; background-color: #d05454;"| |- |Elm || style="width: 30%; background-color: #d05454;"| |- |Elsau || style="width: 30%; background-color: #d05454;"| |- |Embd || style="width: 30%; background-color: #d05454;"| |- |Embrach || style="width: 30%; background-color: #d05454;"| |- |Emdthal || style="width: 30%; background-color: #d05454;"| |- |Emmen || style="width: 30%; background-color: #d05454;"| |- |Emmenbrücke || style="width: 30%; background-color: #d05454;"| |- |Emmenmatt || style="width: 30%; background-color: #d05454;"| |- |Emmetten || style="width: 30%; background-color: #d05454;"| |- |Endingen || style="width: 30%; background-color: #d05454;"| |- |Engelberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Engelburg || style="width: 30%; background-color: #d05454;"| |- |Enges || style="width: 30%; background-color: #d05454;"| |- |Enggistein || style="width: 30%; background-color: #d05454;"| |- |Engi || style="width: 30%; background-color: #d05454;"| |- |Engishofen || style="width: 30%; background-color: #d05454;"| |- |Englisberg || style="width: 30%; background-color: #d05454;"| |- |Engollon || style="width: 30%; background-color: #d05454;"| |- |Engwang || style="width: 30%; background-color: #d05454;"| |- |Engwilen || style="width: 30%; background-color: #d05454;"| |- |Ennenda || style="width: 30%; background-color: #d05454;"| |- |Ennetaach || style="width: 30%; background-color: #d05454;"| |- |Ennetbaden || style="width: 30%; background-color: #d05454;"| |- |Ennetbühl || style="width: 30%; background-color: #d05454;"| |- |Ennetbürgen || style="width: 30%; background-color: #d05454;"| |- |Ennetmoos || style="width: 30%; background-color: #d05454;"| |- |Enney || style="width: 30%; background-color: #d05454;"| |- |Entlebuch || style="width: 30%; background-color: #d05454;"| |- |Epagny || style="width: 30%; background-color: #d05454;"| |- |Epalinges || style="width: 30%; background-color: #d05454;"| |- |Epautheyres || style="width: 30%; background-color: #d05454;"| |- |Epauvillers || style="width: 30%; background-color: #d05454;"| |- |Ependes FR || style="width: 30%; background-color: #d05454;"| |- |Ependes VD || style="width: 30%; background-color: #d05454;"| |- |Epesses || style="width: 30%; background-color: #d05454;"| |- |Epiquerez || style="width: 30%; background-color: #d05454;"| |- |Eppenberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Epsach || style="width: 30%; background-color: #d05454;"| |- |Eptingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Erde || style="width: 30%; background-color: #d05454;"| |- |Ergisch || style="width: 30%; background-color: #d05454;"| |- |Eriswil || style="width: 30%; background-color: #d05454;"| |- |Eriz || style="width: 30%; background-color: #d05454;"| |- |Erlach || style="width: 30%; background-color: #d05454;"| |- |Erlen || style="width: 30%; background-color: #d05454;"| |- |Erlenbach im Simmental || style="width: 30%; background-color: #d05454;"| |- |Erlenbach ZH || style="width: 30%; background-color: #99FF99;"|Argus |- |Erlinsbach AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Erlinsbach SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Ermatingen || style="width: 30%; background-color: #d05454;"| |- |Ermensee || style="width: 30%; background-color: #d05454;"| |- |Ermenswil || style="width: 30%; background-color: #d05454;"| |- |Ernen || style="width: 30%; background-color: #d05454;"| |- |Ernetschwil || style="width: 30%; background-color: #d05454;"| |- |Erschmatt || style="width: 30%; background-color: #d05454;"| |- |Erschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Ersigen || style="width: 30%; background-color: #d05454;"| |- |Erstfeld || style="width: 30%; background-color: #d05454;"| |- |Eschenbach LU || style="width: 30%; background-color: #d05454;"| |- |Eschenbach SG || style="width: 30%; background-color: #d05454;"| |- |Eschenz || style="width: 30%; background-color: #d05454;"| |- |Eschert || style="width: 30%; background-color: #d05454;"| |- |Eschikofen || style="width: 30%; background-color: #d05454;"| |- |Eschlikon TG || style="width: 30%; background-color: #d05454;"| |- |Escholzmatt || style="width: 30%; background-color: #d05454;"| |- |Esmonts || style="width: 30%; background-color: #d05454;"| |- |Essert FR || style="width: 30%; background-color: #d05454;"| |- |Essert-Pittet || style="width: 30%; background-color: #d05454;"| |- |Essert-sous-Champvent || style="width: 30%; background-color: #d05454;"| |- |Essertes || style="width: 30%; background-color: #d05454;"| |- |Essertines-sur-Rolle || style="width: 30%; background-color: #d05454;"| |- |Essertines-sur-Yverdon || style="width: 30%; background-color: #d05454;"| |- |Esslingen || style="width: 30%; background-color: #d05454;"| |- |Estavannens || style="width: 30%; background-color: #d05454;"| |- |Estavayer-le-Gibloux || style="width: 30%; background-color: #d05454;"| |- |Estavayer-le-Lac || style="width: 30%; background-color: #d05454;"| |- |Estévenens || style="width: 30%; background-color: #d05454;"| |- |Etagnières || style="width: 30%; background-color: #d05454;"| |- |Etoy || style="width: 30%; background-color: #d05454;"| |- |Ettenhausen TG || style="width: 30%; background-color: #d05454;"| |- |Ettingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ettiswil || style="width: 30%; background-color: #d05454;"| |- |Etzelkofen || style="width: 30%; background-color: #d05454;"| |- |Etzgen || style="width: 30%; background-color: #99FF99;"|Argus |- |Etziken || style="width: 30%; background-color: #d05454;"| |- |Etzwilen || style="width: 30%; background-color: #d05454;"| |- |Euseigne || style="width: 30%; background-color: #d05454;"| |- |Euthal || style="width: 30%; background-color: #d05454;"| |- |Evilard || style="width: 30%; background-color: #d05454;"| |- |Evionnaz || style="width: 30%; background-color: #d05454;"| |- |Evolène || style="width: 30%; background-color: #d05454;"| |- |Eyholz || style="width: 30%; background-color: #d05454;"| |- |Eysins || style="width: 30%; background-color: #d05454;"| |- |Fahrni b. Thun || style="width: 30%; background-color: #d05454;"| |- |Fahrwangen || style="width: 30%; background-color: #d05454;"| |- |Fahrweid || style="width: 30%; background-color: #99FF99;"|Argus |- |Fahy || style="width: 30%; background-color: #d05454;"| |- |Faido || style="width: 30%; background-color: #d05454;"| |- |Fajauna || style="width: 30%; background-color: #d05454;"| |- |Falera || style="width: 30%; background-color: #d05454;"| |- |Fällanden || style="width: 30%; background-color: #d05454;"| |- |Faltigberg || style="width: 30%; background-color: #d05454;"| |- |Fanas || style="width: 30%; background-color: #d05454;"| |- |Fankhaus (Trub) || style="width: 30%; background-color: #d05454;"| |- |Faoug || style="width: 30%; background-color: #d05454;"| |- |Farden || style="width: 30%; background-color: #d05454;"| |- |Farnern || style="width: 30%; background-color: #d05454;"| |- |Farvagny || style="width: 30%; background-color: #99FF99;"|Argus |- |Farvagny-le-Petit || style="width: 30%; background-color: #d05454;"| |- |Faulensee || style="width: 30%; background-color: #d05454;"| |- |Féchy || style="width: 30%; background-color: #d05454;"| |- |Fehraltorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Fehren || style="width: 30%; background-color: #99FF99;"|Argus |- |Felben-Wellhausen || style="width: 30%; background-color: #d05454;"| |- |Feldbach || style="width: 30%; background-color: #d05454;"| |- |Feldbrunnen || style="width: 30%; background-color: #d05454;"| |- |Feldis/Veulden || style="width: 30%; background-color: #d05454;"| |- |Felsberg || style="width: 30%; background-color: #d05454;"| |- |Felsenau AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Fenalet-sur-Bex || style="width: 30%; background-color: #d05454;"| |- |Fenil-sur-Corsier || style="width: 30%; background-color: #d05454;"| |- |Fenin || style="width: 30%; background-color: #d05454;"| |- |Fenkrieden || style="width: 30%; background-color: #d05454;"| |- |Ferden || style="width: 30%; background-color: #d05454;"| |- |Ferlens VD || style="width: 30%; background-color: #d05454;"| |- |Ferpicloz || style="width: 30%; background-color: #d05454;"| |- |Ferreyres || style="width: 30%; background-color: #d05454;"| |- |Feschel || style="width: 30%; background-color: #d05454;"| |- |Fescoggia || style="width: 30%; background-color: #d05454;"| |- |Fétigny || style="width: 30%; background-color: #d05454;"| |- |Feuerthalen || style="width: 30%; background-color: #d05454;"| |- |Feusisberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Feutersoey || style="width: 30%; background-color: #d05454;"| |- |Fex || style="width: 30%; background-color: #d05454;"| |- |Fey || style="width: 30%; background-color: #d05454;"| |- |Fey (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Fiaugères || style="width: 30%; background-color: #d05454;"| |- |Fidaz || style="width: 30%; background-color: #d05454;"| |- |Fideris || style="width: 30%; background-color: #d05454;"| |- |Fideris Station || style="width: 30%; background-color: #d05454;"| |- |Fiesch || style="width: 30%; background-color: #d05454;"| |- |Fieschertal || style="width: 30%; background-color: #d05454;"| |- |Fiez || style="width: 30%; background-color: #d05454;"| |- |Figino || style="width: 30%; background-color: #d05454;"| |- |Filet || style="width: 30%; background-color: #d05454;"| |- |Filisur || style="width: 30%; background-color: #d05454;"| |- |Filzbach || style="width: 30%; background-color: #d05454;"| |- |Finhaut || style="width: 30%; background-color: #d05454;"| |- |Finsterhennen || style="width: 30%; background-color: #d05454;"| |- |Finstersee || style="width: 30%; background-color: #d05454;"| |- |Finsterwald LU || style="width: 30%; background-color: #d05454;"| |- |Fionnay || style="width: 30%; background-color: #d05454;"| |- |Fischbach LU || style="width: 30%; background-color: #d05454;"| |- |Fischbach-Göslikon || style="width: 30%; background-color: #d05454;"| |- |Fischenthal || style="width: 30%; background-color: #d05454;"| |- |Fischingen || style="width: 30%; background-color: #d05454;"| |- |Fisibach || style="width: 30%; background-color: #d05454;"| |- |Fislisbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Flaach || style="width: 30%; background-color: #d05454;"| |- |Flamatt || style="width: 30%; background-color: #d05454;"| |- |Flanthey || style="width: 30%; background-color: #d05454;"| |- |Fläsch || style="width: 30%; background-color: #d05454;"| |- |Flawil || style="width: 30%; background-color: #d05454;"| |- |Flendruz || style="width: 30%; background-color: #d05454;"| |- |Flerden || style="width: 30%; background-color: #d05454;"| |- |Fleurier || style="width: 30%; background-color: #d05454;"| |- |Flims Dorf || style="width: 30%; background-color: #d05454;"| |- |Flims Waldhaus || style="width: 30%; background-color: #d05454;"| |- |Flond || style="width: 30%; background-color: #d05454;"| |- |Flüelen || style="width: 30%; background-color: #d05454;"| |- |Flüeli-Ranft || style="width: 30%; background-color: #d05454;"| |- |Flüh || style="width: 30%; background-color: #99FF99;"|Argus |- |Flühli LU || style="width: 30%; background-color: #d05454;"| |- |Flumenthal || style="width: 30%; background-color: #d05454;"| |- |Flums || style="width: 30%; background-color: #d05454;"| |- |Flums Hochwiese || style="width: 30%; background-color: #d05454;"| |- |Flumserberg Bergheim || style="width: 30%; background-color: #d05454;"| |- |Flumserberg Portels || style="width: 30%; background-color: #d05454;"| |- |Flumserberg Saxli || style="width: 30%; background-color: #d05454;"| |- |Flumserberg Tannenbodenalp || style="width: 30%; background-color: #d05454;"| |- |Flumserberg Tannenheim || style="width: 30%; background-color: #d05454;"| |- |Flurlingen || style="width: 30%; background-color: #d05454;"| |- |Font || style="width: 30%; background-color: #d05454;"| |- |Fontaine Dessous (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Fontaine Dessus (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Fontainemelon || style="width: 30%; background-color: #d05454;"| |- |Fontaines NE || style="width: 30%; background-color: #d05454;"| |- |Fontaines-sur-Grandson || style="width: 30%; background-color: #d05454;"| |- |Fontanezier || style="width: 30%; background-color: #d05454;"| |- |Fontannen || style="width: 30%; background-color: #d05454;"| |- |Fontenais || style="width: 30%; background-color: #d05454;"| |- |Fontenelle || style="width: 30%; background-color: #d05454;"| |- |Fontnas || style="width: 30%; background-color: #d05454;"| |- |Forch || style="width: 30%; background-color: #d05454;"| |- |Forel (Lavaux) || style="width: 30%; background-color: #d05454;"| |- |Forel FR || style="width: 30%; background-color: #d05454;"| |- |Forel-sur-Lucens || style="width: 30%; background-color: #d05454;"| |- |Formangueires || style="width: 30%; background-color: #d05454;"| |- |Fornet-Dessous || style="width: 30%; background-color: #d05454;"| |- |Fornet-Dessus || style="width: 30%; background-color: #d05454;"| |- |Fornex (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Forst || style="width: 30%; background-color: #d05454;"| |- |Fortunau (Ayent) || style="width: 30%; background-color: #d05454;"| |- |Founex || style="width: 30%; background-color: #d05454;"| |- |Fräschels || style="width: 30%; background-color: #d05454;"| |- |Frasco || style="width: 30%; background-color: #d05454;"| |- |Frasnacht || style="width: 30%; background-color: #d05454;"| |- |Frasses || style="width: 30%; background-color: #d05454;"| |- |Fraubrunnen || style="width: 30%; background-color: #d05454;"| |- |Frauenfeld || style="width: 30%; background-color: #d05454;"| |- |Frauenkappelen || style="width: 30%; background-color: #d05454;"| |- |Fregiécourt || style="width: 30%; background-color: #d05454;"| |- |Freidorf TG || style="width: 30%; background-color: #d05454;"| |- |Freienbach || style="width: 30%; background-color: #d05454;"| |- |Freienstein || style="width: 30%; background-color: #d05454;"| |- |Freienwil || style="width: 30%; background-color: #d05454;"| |- |Freimettigen || style="width: 30%; background-color: #d05454;"| |- |Frenières-sur-Bex || style="width: 30%; background-color: #d05454;"| |- |Frenkendorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Fresens || style="width: 30%; background-color: #d05454;"| |- |Fretereules || style="width: 30%; background-color: #d05454;"| |- |Freudwil || style="width: 30%; background-color: #d05454;"| |- |Fribourg || style="width: 30%; background-color: #d05454;"| |- |Frick || style="width: 30%; background-color: #99FF99;"|Argus |- |Frieswil || style="width: 30%; background-color: #d05454;"| |- |Friltschen || style="width: 30%; background-color: #d05454;"| |- |Frinvillier || style="width: 30%; background-color: #d05454;"| |- |Froideville || style="width: 30%; background-color: #d05454;"| |- |Frümsen || style="width: 30%; background-color: #d05454;"| |- |Fruthwilen || style="width: 30%; background-color: #d05454;"| |- |Frutigen || style="width: 30%; background-color: #d05454;"| |- |Ftan || style="width: 30%; background-color: #d05454;"| |- |Fuldera || style="width: 30%; background-color: #d05454;"| |- |Fulenbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Full-Reuenthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Füllinsdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Fully || style="width: 30%; background-color: #d05454;"| |- |Fürigen || style="width: 30%; background-color: #d05454;"| |- |Furna || style="width: 30%; background-color: #d05454;"| |- |Fürstenau || style="width: 30%; background-color: #d05454;"| |- |Fürstenaubruck || style="width: 30%; background-color: #d05454;"| |- |Fusio || style="width: 30%; background-color: #d05454;"| |- |Gabi (Simplon) || style="width: 30%; background-color: #d05454;"| |- |Gächlingen || style="width: 30%; background-color: #d05454;"| |- |Gächliwil || style="width: 30%; background-color: #d05454;"| |- |Gachnang || style="width: 30%; background-color: #d05454;"| |- |Gadenstätt || style="width: 30%; background-color: #d05454;"| |- |Gadmen || style="width: 30%; background-color: #d05454;"| |- |Gähwil || style="width: 30%; background-color: #d05454;"| |- |Gais || style="width: 30%; background-color: #d05454;"| |- |Gaiserwald || style="width: 30%; background-color: #d05454;"| |- |Galgenen || style="width: 30%; background-color: #d05454;"| |- |Galmiz || style="width: 30%; background-color: #d05454;"| |- |Gals || style="width: 30%; background-color: #d05454;"| |- |Gampel || style="width: 30%; background-color: #d05454;"| |- |Gampelen || style="width: 30%; background-color: #d05454;"| |- |Gams || style="width: 30%; background-color: #d05454;"| |- |Gamsen || style="width: 30%; background-color: #d05454;"| |- |Gandria || style="width: 30%; background-color: #d05454;"| |- |Gänsbrunnen || style="width: 30%; background-color: #d05454;"| |- |Gansingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ganterschwil || style="width: 30%; background-color: #d05454;"| |- |Gasel || style="width: 30%; background-color: #99FF99;"|Argus |- |Gasenried || style="width: 30%; background-color: #d05454;"| |- |Gattikon || style="width: 30%; background-color: #d05454;"| |- |Gebenstorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Gebertingen || style="width: 30%; background-color: #d05454;"| |- |Geiss || style="width: 30%; background-color: #d05454;"| |- |Gelfingen || style="width: 30%; background-color: #d05454;"| |- |Gelterfingen || style="width: 30%; background-color: #d05454;"| |- |Gelterkinden || style="width: 30%; background-color: #99FF99;"|Argus |- |Geltwil || style="width: 30%; background-color: #d05454;"| |- |Gempen || style="width: 30%; background-color: #99FF99;"|Argus |- |Gempenach || style="width: 30%; background-color: #d05454;"| |- |Genestrerio || style="width: 30%; background-color: #d05454;"| |- |Genève || style="width: 30%; background-color: #d05454;"| |- |Geneveys-sur-Coffrane || style="width: 30%; background-color: #d05454;"| |- |Genolier || style="width: 30%; background-color: #d05454;"| |- |Genthod || style="width: 30%; background-color: #d05454;"| |- |Gentilino || style="width: 30%; background-color: #d05454;"| |- |Gerlafingen || style="width: 30%; background-color: #d05454;"| |- |Gerlikon || style="width: 30%; background-color: #d05454;"| |- |Geroldswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Gerolfingen || style="width: 30%; background-color: #d05454;"| |- |Gerra (Gambarogno) || style="width: 30%; background-color: #d05454;"| |- |Gerra (Verzasca) || style="width: 30%; background-color: #d05454;"| |- |Gersau || style="width: 30%; background-color: #d05454;"| |- |Gerzensee || style="width: 30%; background-color: #d05454;"| |- |Geschinen || style="width: 30%; background-color: #d05454;"| |- |Gettnau || style="width: 30%; background-color: #d05454;"| |- |Geuensee || style="width: 30%; background-color: #d05454;"| |- |Ghirone || style="width: 30%; background-color: #d05454;"| |- |Gibswil || style="width: 30%; background-color: #d05454;"| |- |Giebenach || style="width: 30%; background-color: #d05454;"| |- |Giez || style="width: 30%; background-color: #d05454;"| |- |Giffers || style="width: 30%; background-color: #d05454;"| |- |Gillarens || style="width: 30%; background-color: #d05454;"| |- |Gilly || style="width: 30%; background-color: #d05454;"| |- |Gimel || style="width: 30%; background-color: #d05454;"| |- |Gimmelwald || style="width: 30%; background-color: #d05454;"| |- |Gingins || style="width: 30%; background-color: #d05454;"| |- |Giornico || style="width: 30%; background-color: #d05454;"| |- |Gipf-Oberfrick || style="width: 30%; background-color: #99FF99;"|Argus |- |Gisikon || style="width: 30%; background-color: #d05454;"| |- |Giswil || style="width: 30%; background-color: #d05454;"| |- |Giubiasco || style="width: 30%; background-color: #d05454;"| |- |Giumaglio || style="width: 30%; background-color: #d05454;"| |- |Givisiez || style="width: 30%; background-color: #d05454;"| |- |Givrins || style="width: 30%; background-color: #d05454;"| |- |Gland || style="width: 30%; background-color: #d05454;"| |- |Glarus || style="width: 30%; background-color: #d05454;"| |- |Glashütten || style="width: 30%; background-color: #d05454;"| |- |Glaspass || style="width: 30%; background-color: #d05454;"| |- |Glattbrugg || style="width: 30%; background-color: #d05454;"| |- |Glattfelden || style="width: 30%; background-color: #d05454;"| |- |Glattpark (Opfikon) || style="width: 30%; background-color: #d05454;"| |- |Gletterens || style="width: 30%; background-color: #d05454;"| |- |Glion || style="width: 30%; background-color: #d05454;"| |- |Glis || style="width: 30%; background-color: #d05454;"| |- |Glovelier || style="width: 30%; background-color: #d05454;"| |- |Gluringen || style="width: 30%; background-color: #d05454;"| |- |Gnosca || style="width: 30%; background-color: #d05454;"| |- |Gockhausen || style="width: 30%; background-color: #99FF99;"|Argus |- |Gohl || style="width: 30%; background-color: #d05454;"| |- |Golaten || style="width: 30%; background-color: #d05454;"| |- |Goldach || style="width: 30%; background-color: #d05454;"| |- |Goldau || style="width: 30%; background-color: #d05454;"| |- |Goldingen || style="width: 30%; background-color: #d05454;"| |- |Goldiwil (Thun) || style="width: 30%; background-color: #99FF99;"|Argus |- |Goldswil || style="width: 30%; background-color: #d05454;"| |- |Golino || style="width: 30%; background-color: #d05454;"| |- |Gollion || style="width: 30%; background-color: #d05454;"| |- |Gommiswald || style="width: 30%; background-color: #d05454;"| |- |Gondiswil || style="width: 30%; background-color: #d05454;"| |- |Gondo || style="width: 30%; background-color: #d05454;"| |- |Gonten || style="width: 30%; background-color: #d05454;"| |- |Gontenbad || style="width: 30%; background-color: #d05454;"| |- |Gontenschwil || style="width: 30%; background-color: #d05454;"| |- |Goppenstein || style="width: 30%; background-color: #d05454;"| |- |Goppisberg || style="width: 30%; background-color: #d05454;"| |- |Gordevio || style="width: 30%; background-color: #d05454;"| |- |Gordola || style="width: 30%; background-color: #d05454;"| |- |Gorduno || style="width: 30%; background-color: #d05454;"| |- |Gorgier || style="width: 30%; background-color: #d05454;"| |- |Gornergrat || style="width: 30%; background-color: #d05454;"| |- |Göschenen || style="width: 30%; background-color: #d05454;"| |- |Gossau SG || style="width: 30%; background-color: #d05454;"| |- |Gossau ZH || style="width: 30%; background-color: #d05454;"| |- |Gossens || style="width: 30%; background-color: #d05454;"| |- |Gossliwil || style="width: 30%; background-color: #d05454;"| |- |Götighofen || style="width: 30%; background-color: #d05454;"| |- |Gottlieben || style="width: 30%; background-color: #d05454;"| |- |Goumoens-la-Ville || style="width: 30%; background-color: #d05454;"| |- |Goumoens-le-Jux || style="width: 30%; background-color: #d05454;"| |- |Goumois || style="width: 30%; background-color: #d05454;"| |- |Graben || style="width: 30%; background-color: #d05454;"| |- |Grabs || style="width: 30%; background-color: #d05454;"| |- |Grabserberg || style="width: 30%; background-color: #d05454;"| |- |Grächen || style="width: 30%; background-color: #d05454;"| |- |Grafenort || style="width: 30%; background-color: #d05454;"| |- |Grafenried || style="width: 30%; background-color: #d05454;"| |- |Grafstal || style="width: 30%; background-color: #d05454;"| |- |Graltshausen || style="width: 30%; background-color: #d05454;"| |- |Grancia || style="width: 30%; background-color: #d05454;"| |- |Grancy || style="width: 30%; background-color: #d05454;"| |- |Grand-Lancy || style="width: 30%; background-color: #d05454;"| |- |Grandcour || style="width: 30%; background-color: #d05454;"| |- |Grandevent || style="width: 30%; background-color: #d05454;"| |- |Grandfontaine || style="width: 30%; background-color: #d05454;"| |- |Grandsivaz || style="width: 30%; background-color: #d05454;"| |- |Grandson || style="width: 30%; background-color: #d05454;"| |- |Grandval || style="width: 30%; background-color: #d05454;"| |- |Grandvaux || style="width: 30%; background-color: #d05454;"| |- |Grandvillard || style="width: 30%; background-color: #d05454;"| |- |Granges (Salvan) || style="width: 30%; background-color: #d05454;"| |- |Granges (Veveyse) || style="width: 30%; background-color: #d05454;"| |- |Granges VS || style="width: 30%; background-color: #d05454;"| |- |Granges-de-Vesin || style="width: 30%; background-color: #d05454;"| |- |Granges-Paccot || style="width: 30%; background-color: #d05454;"| |- |Granges-près-Marnand || style="width: 30%; background-color: #d05454;"| |- |Grangettes || style="width: 30%; background-color: #d05454;"| |- |Gränichen || style="width: 30%; background-color: #d05454;"| |- |Granois (Savièse) || style="width: 30%; background-color: #d05454;"| |- |Gräslikon || style="width: 30%; background-color: #d05454;"| |- |Grasswil || style="width: 30%; background-color: #d05454;"| |- |Grattavache || style="width: 30%; background-color: #d05454;"| |- |Gravesano || style="width: 30%; background-color: #d05454;"| |- |Greich || style="width: 30%; background-color: #d05454;"| |- |Greifensee || style="width: 30%; background-color: #d05454;"| |- |Grellingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Grenchen || style="width: 30%; background-color: #99FF99;"|Argus |- |Greng || style="width: 30%; background-color: #d05454;"| |- |Grengiols || style="width: 30%; background-color: #d05454;"| |- |Grenilles || style="width: 30%; background-color: #d05454;"| |- |Grens || style="width: 30%; background-color: #d05454;"| |- |Greppen || style="width: 30%; background-color: #d05454;"| |- |Gresso || style="width: 30%; background-color: #d05454;"| |- |Gressy || style="width: 30%; background-color: #d05454;"| |- |Gretschins || style="width: 30%; background-color: #d05454;"| |- |Gretzenbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Griesenberg || style="width: 30%; background-color: #d05454;"| |- |Grimentz || style="width: 30%; background-color: #d05454;"| |- |Grimisuat || style="width: 30%; background-color: #d05454;"| |- |Grimmialp || style="width: 30%; background-color: #d05454;"| |- |Grindel || style="width: 30%; background-color: #99FF99;"|Argus |- |Grindelwald || style="width: 30%; background-color: #d05454;"| |- |Grolley || style="width: 30%; background-color: #d05454;"| |- |Grône || style="width: 30%; background-color: #d05454;"| |- |Grono || style="width: 30%; background-color: #d05454;"| |- |Gross || style="width: 30%; background-color: #d05454;"| |- |Grossaffoltern || style="width: 30%; background-color: #d05454;"| |- |Grossdietwil || style="width: 30%; background-color: #d05454;"| |- |Grosshöchstetten || style="width: 30%; background-color: #d05454;"| |- |Grosswangen || style="width: 30%; background-color: #d05454;"| |- |Grub AR || style="width: 30%; background-color: #d05454;"| |- |Grub SG || style="width: 30%; background-color: #d05454;"| |- |Gruben || style="width: 30%; background-color: #d05454;"| |- |Grugnay (Chamoson) || style="width: 30%; background-color: #d05454;"| |- |Grund b. Gstaad || style="width: 30%; background-color: #d05454;"| |- |Grünen || style="width: 30%; background-color: #d05454;"| |- |Grünenmatt || style="width: 30%; background-color: #d05454;"| |- |Grüningen || style="width: 30%; background-color: #d05454;"| |- |Grüsch || style="width: 30%; background-color: #d05454;"| |- |Grüt (Gossau ZH) || style="width: 30%; background-color: #d05454;"| |- |Gruyères || style="width: 30%; background-color: #d05454;"| |- |Gryon || style="width: 30%; background-color: #d05454;"| |- |Gstaad || style="width: 30%; background-color: #d05454;"| |- |Gsteig b. Gstaad || style="width: 30%; background-color: #d05454;"| |- |Gsteigwiler || style="width: 30%; background-color: #d05454;"| |- |Guarda || style="width: 30%; background-color: #d05454;"| |- |Gudo || style="width: 30%; background-color: #d05454;"| |- |Guggisberg || style="width: 30%; background-color: #d05454;"| |- |Gumefens || style="width: 30%; background-color: #99FF99;"|Argus |- |Gümligen || style="width: 30%; background-color: #d05454;"| |- |Gümmenen || style="width: 30%; background-color: #d05454;"| |- |Gundetswil || style="width: 30%; background-color: #d05454;"| |- |Gündlischwand || style="width: 30%; background-color: #d05454;"| |- |Günsberg || style="width: 30%; background-color: #d05454;"| |- |Guntalingen || style="width: 30%; background-color: #d05454;"| |- |Gunten || style="width: 30%; background-color: #d05454;"| |- |Guntershausen b. Aadorf || style="width: 30%; background-color: #d05454;"| |- |Gunterswilen || style="width: 30%; background-color: #d05454;"| |- |Guntmadingen || style="width: 30%; background-color: #d05454;"| |- |Gunzgen || style="width: 30%; background-color: #99FF99;"|Argus |- |Gunzwil || style="width: 30%; background-color: #d05454;"| |- |Gurbrü || style="width: 30%; background-color: #d05454;"| |- |Gurmels || style="width: 30%; background-color: #d05454;"| |- |Gurtnellen || style="width: 30%; background-color: #d05454;"| |- |Gurzelen || style="width: 30%; background-color: #d05454;"| |- |Guschelmuth || style="width: 30%; background-color: #d05454;"| |- |Gutenburg || style="width: 30%; background-color: #d05454;"| |- |Gutenswil || style="width: 30%; background-color: #d05454;"| |- |Guttannen || style="width: 30%; background-color: #d05454;"| |- |Guttet || style="width: 30%; background-color: #d05454;"| |- |Güttingen || style="width: 30%; background-color: #d05454;"| |- |Gwatt (Thun) || style="width: 30%; background-color: #d05454;"| |- |Gy || style="width: 30%; background-color: #d05454;"| |- |Gysenstein || style="width: 30%; background-color: #d05454;"| |- |Haag (Rheintal) || style="width: 30%; background-color: #d05454;"| |- |Habkern || style="width: 30%; background-color: #d05454;"| |- |Habsburg || style="width: 30%; background-color: #99FF99;"|Argus |- |Häfelfingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Hagenbuch ZH || style="width: 30%; background-color: #d05454;"| |- |Hägendorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Hagendorn || style="width: 30%; background-color: #d05454;"| |- |Hagenwil b. Amriswil || style="width: 30%; background-color: #d05454;"| |- |Häggenschwil || style="width: 30%; background-color: #d05454;"| |- |Hägglingen || style="width: 30%; background-color: #d05454;"| |- |Hagneck || style="width: 30%; background-color: #d05454;"| |- |Halden || style="width: 30%; background-color: #d05454;"| |- |Haldenstein || style="width: 30%; background-color: #d05454;"| |- |Haldi b. Schattdorf || style="width: 30%; background-color: #d05454;"| |- |Hallau || style="width: 30%; background-color: #d05454;"| |- |Hallwil || style="width: 30%; background-color: #d05454;"| |- |Halten || style="width: 30%; background-color: #d05454;"| |- |Hämikon || style="width: 30%; background-color: #d05454;"| |- |Happerswil || style="width: 30%; background-color: #d05454;"| |- |Hard b. Weinfelden || style="width: 30%; background-color: #d05454;"| |- |Harenwilen || style="width: 30%; background-color: #d05454;"| |- |Härkingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Hasle b. Burgdorf || style="width: 30%; background-color: #d05454;"| |- |Hasle LU || style="width: 30%; background-color: #d05454;"| |- |Haslen AI || style="width: 30%; background-color: #d05454;"| |- |Haslen GL || style="width: 30%; background-color: #d05454;"| |- |Hasliberg Goldern || style="width: 30%; background-color: #d05454;"| |- |Hasliberg Hohfluh || style="width: 30%; background-color: #d05454;"| |- |Hasliberg Reuti || style="width: 30%; background-color: #d05454;"| |- |Hasliberg Wasserwendi || style="width: 30%; background-color: #d05454;"| |- |Hattenhausen || style="width: 30%; background-color: #d05454;"| |- |Hätzingen || style="width: 30%; background-color: #d05454;"| |- |Hauenstein || style="width: 30%; background-color: #99FF99;"|Argus |- |Hauptikon || style="width: 30%; background-color: #d05454;"| |- |Hauptwil || style="width: 30%; background-color: #d05454;"| |- |Hausen AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Hausen am Albis || style="width: 30%; background-color: #99FF99;"|Argus |- |Häusernmoos || style="width: 30%; background-color: #d05454;"| |- |Häuslenen || style="width: 30%; background-color: #d05454;"| |- |Haute-Nendaz || style="width: 30%; background-color: #d05454;"| |- |Hauterive NE || style="width: 30%; background-color: #d05454;"| |- |Hauteville || style="width: 30%; background-color: #d05454;"| |- |Häutligen || style="width: 30%; background-color: #d05454;"| |- |Hedingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Heerbrugg || style="width: 30%; background-color: #d05454;"| |- |Hefenhausen || style="width: 30%; background-color: #d05454;"| |- |Hefenhofen || style="width: 30%; background-color: #d05454;"| |- |Heiden || style="width: 30%; background-color: #d05454;"| |- |Heiligenschwendi || style="width: 30%; background-color: #d05454;"| |- |Heiligkreuz (Mels) || style="width: 30%; background-color: #d05454;"| |- |Heimberg || style="width: 30%; background-color: #d05454;"| |- |Heimenhausen || style="width: 30%; background-color: #d05454;"| |- |Heimenschwand || style="width: 30%; background-color: #d05454;"| |- |Heimisbach || style="width: 30%; background-color: #d05454;"| |- |Heimiswil || style="width: 30%; background-color: #d05454;"| |- |Heinrichswil || style="width: 30%; background-color: #d05454;"| |- |Heitenried || style="width: 30%; background-color: #d05454;"| |- |Heldswil || style="width: 30%; background-color: #d05454;"| |- |Helgisried-Rohrbach || style="width: 30%; background-color: #d05454;"| |- |Hellbühl || style="width: 30%; background-color: #d05454;"| |- |Hellikon || style="width: 30%; background-color: #d05454;"| |- |Hellsau || style="width: 30%; background-color: #d05454;"| |- |Hemberg || style="width: 30%; background-color: #d05454;"| |- |Hemishofen || style="width: 30%; background-color: #d05454;"| |- |Hemmental || style="width: 30%; background-color: #d05454;"| |- |Hemmiken || style="width: 30%; background-color: #99FF99;"|Argus |- |Henau || style="width: 30%; background-color: #d05454;"| |- |Hendschiken || style="width: 30%; background-color: #99FF99;"|Argus |- |Henggart || style="width: 30%; background-color: #d05454;"| |- |Hennens || style="width: 30%; background-color: #d05454;"| |- |Henniez || style="width: 30%; background-color: #d05454;"| |- |Herbetswil || style="width: 30%; background-color: #d05454;"| |- |Herbligen || style="width: 30%; background-color: #d05454;"| |- |Herbriggen || style="width: 30%; background-color: #d05454;"| |- |Herdern || style="width: 30%; background-color: #d05454;"| |- |Hérémence || style="width: 30%; background-color: #d05454;"| |- |Hergiswil b. Willisau || style="width: 30%; background-color: #d05454;"| |- |Hergiswil NW || style="width: 30%; background-color: #d05454;"| |- |Herisau || style="width: 30%; background-color: #d05454;"| |- |Herlisberg || style="width: 30%; background-color: #d05454;"| |- |Hermance || style="width: 30%; background-color: #d05454;"| |- |Hermatswil || style="width: 30%; background-color: #d05454;"| |- |Hermenches || style="width: 30%; background-color: #d05454;"| |- |Hermetschwil-Staffeln || style="width: 30%; background-color: #d05454;"| |- |Hermiswil || style="width: 30%; background-color: #d05454;"| |- |Hermrigen || style="width: 30%; background-color: #d05454;"| |- |Herrenhof || style="width: 30%; background-color: #d05454;"| |- |Herrenschwanden || style="width: 30%; background-color: #d05454;"| |- |Herrliberg || style="width: 30%; background-color: #d05454;"| |- |Hersberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Hersiwil || style="width: 30%; background-color: #d05454;"| |- |Hertenstein AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Herznach || style="width: 30%; background-color: #99FF99;"|Argus |- |Herzogenbuchsee || style="width: 30%; background-color: #d05454;"| |- |Hessigkofen || style="width: 30%; background-color: #d05454;"| |- |Hettenschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Hettiswil || style="width: 30%; background-color: #d05454;"| |- |Hettlingen || style="width: 30%; background-color: #d05454;"| |- |Hildisrieden || style="width: 30%; background-color: #d05454;"| |- |Hilfikon || style="width: 30%; background-color: #d05454;"| |- |Hilterfingen || style="width: 30%; background-color: #d05454;"| |- |Himmelried || style="width: 30%; background-color: #99FF99;"|Argus |- |Hindelbank || style="width: 30%; background-color: #d05454;"| |- |Hinterforst || style="width: 30%; background-color: #d05454;"| |- |Hinterfultigen || style="width: 30%; background-color: #d05454;"| |- |Hinterkappelen || style="width: 30%; background-color: #d05454;"| |- |Hintermoos || style="width: 30%; background-color: #d05454;"| |- |Hinterrhein || style="width: 30%; background-color: #d05454;"| |- |Hinwil || style="width: 30%; background-color: #d05454;"| |- |Hirschthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Hirzel || style="width: 30%; background-color: #d05454;"| |- |Hittnau || style="width: 30%; background-color: #d05454;"| |- |Hitzkirch || style="width: 30%; background-color: #d05454;"| |- |Hochdorf || style="width: 30%; background-color: #d05454;"| |- |Hochfelden || style="width: 30%; background-color: #d05454;"| |- |Höchstetten || style="width: 30%; background-color: #d05454;"| |- |Hochwald || style="width: 30%; background-color: #99FF99;"|Argus |- |Höfen b. Thun || style="width: 30%; background-color: #d05454;"| |- |Hofen SH || style="width: 30%; background-color: #d05454;"| |- |Hoffeld || style="width: 30%; background-color: #d05454;"| |- |Hofstatt || style="width: 30%; background-color: #d05454;"| |- |Hofstetten b. Brienz || style="width: 30%; background-color: #d05454;"| |- |Hofstetten BE || style="width: 30%; background-color: #d05454;"| |- |Hofstetten SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Hofstetten ZH || style="width: 30%; background-color: #d05454;"| |- |Hohenrain || style="width: 30%; background-color: #d05454;"| |- |Hohentannen || style="width: 30%; background-color: #d05454;"| |- |Hohtenn || style="width: 30%; background-color: #d05454;"| |- |Holderbank AG || style="width: 30%; background-color: #d05454;"| |- |Holderbank SO || style="width: 30%; background-color: #d05454;"| |- |Hölstein || style="width: 30%; background-color: #99FF99;"|Argus |- |Holzhäusern ZG || style="width: 30%; background-color: #d05454;"| |- |Holziken || style="width: 30%; background-color: #d05454;"| |- |Homberg b. Thun || style="width: 30%; background-color: #d05454;"| |- |Hombrechtikon || style="width: 30%; background-color: #d05454;"| |- |Homburg || style="width: 30%; background-color: #d05454;"| |- |Honau || style="width: 30%; background-color: #d05454;"| |- |Hondrich || style="width: 30%; background-color: #d05454;"| |- |Horboden || style="width: 30%; background-color: #d05454;"| |- |Horgen || style="width: 30%; background-color: #99FF99;"|Argus |- |Horgenberg || style="width: 30%; background-color: #d05454;"| |- |Hörhausen || style="width: 30%; background-color: #d05454;"| |- |Höri || style="width: 30%; background-color: #d05454;"| |- |Horn || style="width: 30%; background-color: #d05454;"| |- |Hornussen || style="width: 30%; background-color: #99FF99;"|Argus |- |Horrenbach || style="width: 30%; background-color: #d05454;"| |- |Horriwil || style="width: 30%; background-color: #d05454;"| |- |Horw || style="width: 30%; background-color: #d05454;"| |- |Hosenruck || style="width: 30%; background-color: #d05454;"| |- |Hospental || style="width: 30%; background-color: #d05454;"| |- |Hottwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Hubersdorf || style="width: 30%; background-color: #d05454;"| |- |Huémoz || style="width: 30%; background-color: #d05454;"| |- |Hugelshofen || style="width: 30%; background-color: #d05454;"| |- |Humlikon || style="width: 30%; background-color: #d05454;"| |- |Hundwil || style="width: 30%; background-color: #d05454;"| |- |Hünenberg || style="width: 30%; background-color: #d05454;"| |- |Hünibach || style="width: 30%; background-color: #d05454;"| |- |Hüniken || style="width: 30%; background-color: #d05454;"| |- |Hüntwangen || style="width: 30%; background-color: #d05454;"| |- |Hunzenschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Hurden || style="width: 30%; background-color: #d05454;"| |- |Hüswil || style="width: 30%; background-color: #d05454;"| |- |Hütten || style="width: 30%; background-color: #d05454;"| |- |Hüttikon || style="width: 30%; background-color: #d05454;"| |- |Hüttlingen || style="width: 30%; background-color: #d05454;"| |- |Huttwil || style="width: 30%; background-color: #d05454;"| |- |Hüttwilen || style="width: 30%; background-color: #d05454;"| |- |Ibach || style="width: 30%; background-color: #d05454;"| |- |Ichertswil || style="width: 30%; background-color: #d05454;"| |- |Icogne || style="width: 30%; background-color: #d05454;"| |- |Iffwil || style="width: 30%; background-color: #d05454;"| |- |Igis || style="width: 30%; background-color: #d05454;"| |- |Ilanz || style="width: 30%; background-color: #d05454;"| |- |Illgau || style="width: 30%; background-color: #d05454;"| |- |Illhart || style="width: 30%; background-color: #d05454;"| |- |Illighausen || style="width: 30%; background-color: #d05454;"| |- |Illnau || style="width: 30%; background-color: #d05454;"| |- |Im Fang || style="width: 30%; background-color: #d05454;"| |- |Immensee || style="width: 30%; background-color: #d05454;"| |- |Indemini || style="width: 30%; background-color: #d05454;"| |- |Inden || style="width: 30%; background-color: #d05454;"| |- |Inkwil || style="width: 30%; background-color: #d05454;"| |- |Innerberg || style="width: 30%; background-color: #d05454;"| |- |Innereriz || style="width: 30%; background-color: #d05454;"| |- |Innerferrera || style="width: 30%; background-color: #d05454;"| |- |Innerthal || style="width: 30%; background-color: #d05454;"| |- |Innertkirchen || style="width: 30%; background-color: #d05454;"| |- |Ins || style="width: 30%; background-color: #d05454;"| |- |Insone || style="width: 30%; background-color: #d05454;"| |- |Interlaken || style="width: 30%; background-color: #d05454;"| |- |Intragna || style="width: 30%; background-color: #d05454;"| |- |Intschi || style="width: 30%; background-color: #d05454;"| |- |Inwil || style="width: 30%; background-color: #d05454;"| |- |Ipsach || style="width: 30%; background-color: #d05454;"| |- |Iragna || style="width: 30%; background-color: #d05454;"| |- |Iseltwald || style="width: 30%; background-color: #d05454;"| |- |Isenfluh || style="width: 30%; background-color: #d05454;"| |- |Isenthal || style="width: 30%; background-color: #d05454;"| |- |Iseo || style="width: 30%; background-color: #d05454;"| |- |Isérables || style="width: 30%; background-color: #d05454;"| |- |Islikon || style="width: 30%; background-color: #d05454;"| |- |Islisberg || style="width: 30%; background-color: #d05454;"| |- |Isole di Brissago || style="width: 30%; background-color: #d05454;"| |- |Isone || style="width: 30%; background-color: #d05454;"| |- |Istighofen || style="width: 30%; background-color: #d05454;"| |- |Itingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ittenthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Ittigen || style="width: 30%; background-color: #d05454;"| |- |Jaberg || style="width: 30%; background-color: #d05454;"| |- |Jakobsbad || style="width: 30%; background-color: #d05454;"| |- |Jaun || style="width: 30%; background-color: #d05454;"| |- |Jegenstorf || style="width: 30%; background-color: #d05454;"| |- |Jenaz || style="width: 30%; background-color: #d05454;"| |- |Jenins || style="width: 30%; background-color: #d05454;"| |- |Jens || style="width: 30%; background-color: #d05454;"| |- |Jeuss || style="width: 30%; background-color: #d05454;"| |- |Jona || style="width: 30%; background-color: #d05454;"| |- |Jonen || style="width: 30%; background-color: #d05454;"| |- |Jongny || style="width: 30%; background-color: #d05454;"| |- |Jonschwil || style="width: 30%; background-color: #d05454;"| |- |Jouxtens-Mézery || style="width: 30%; background-color: #d05454;"| |- |Juf || style="width: 30%; background-color: #d05454;"| |- |Jungfraujoch || style="width: 30%; background-color: #d05454;"| |- |Juriens || style="width: 30%; background-color: #d05454;"| |- |Jussy || style="width: 30%; background-color: #d05454;"| |- |Kägiswil || style="width: 30%; background-color: #d05454;"| |- |Kaiseraugst || style="width: 30%; background-color: #99FF99;"|Argus |- |Kaiserstuhl AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Kaisten || style="width: 30%; background-color: #99FF99;"|Argus |- |Kallern || style="width: 30%; background-color: #d05454;"| |- |Kallnach || style="width: 30%; background-color: #d05454;"| |- |Kalpetran || style="width: 30%; background-color: #d05454;"| |- |Kaltacker || style="width: 30%; background-color: #d05454;"| |- |Kaltbach || style="width: 30%; background-color: #d05454;"| |- |Kaltbrunn || style="width: 30%; background-color: #d05454;"| |- |Kaltenbach || style="width: 30%; background-color: #d05454;"| |- |Kammersrohr || style="width: 30%; background-color: #d05454;"| |- |Kandergrund || style="width: 30%; background-color: #d05454;"| |- |Kandersteg || style="width: 30%; background-color: #d05454;"| |- |Känerkinden || style="width: 30%; background-color: #99FF99;"|Argus |- |Kappel am Albis || style="width: 30%; background-color: #d05454;"| |- |Kappel SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Kappelen || style="width: 30%; background-color: #d05454;"| |- |Kastanienbaum || style="width: 30%; background-color: #d05454;"| |- |Kaufdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Kefikon || style="width: 30%; background-color: #d05454;"| |- |Kehrsatz || style="width: 30%; background-color: #d05454;"| |- |Kehrsiten || style="width: 30%; background-color: #d05454;"| |- |Kemptthal || style="width: 30%; background-color: #d05454;"| |- |Kernenried || style="width: 30%; background-color: #d05454;"| |- |Kerns || style="width: 30%; background-color: #d05454;"| |- |Kerzers || style="width: 30%; background-color: #d05454;"| |- |Kesswil || style="width: 30%; background-color: #d05454;"| |- |Kestenholz || style="width: 30%; background-color: #99FF99;"|Argus |- |Kienberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Kienersrüti || style="width: 30%; background-color: #d05454;"| |- |Kiental || style="width: 30%; background-color: #d05454;"| |- |Kiesen || style="width: 30%; background-color: #d05454;"| |- |Kilchberg BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Kilchberg ZH || style="width: 30%; background-color: #d05454;"| |- |Killwangen || style="width: 30%; background-color: #99FF99;"|Argus |- |Kippel || style="width: 30%; background-color: #d05454;"| |- |Kirchberg BE || style="width: 30%; background-color: #d05454;"| |- |Kirchberg SG || style="width: 30%; background-color: #d05454;"| |- |Kirchdorf AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Kirchdorf BE || style="width: 30%; background-color: #d05454;"| |- |Kirchenthurnen || style="width: 30%; background-color: #d05454;"| |- |Kirchleerau || style="width: 30%; background-color: #d05454;"| |- |Kirchlindach || style="width: 30%; background-color: #d05454;"| |- |Klarsreuti || style="width: 30%; background-color: #d05454;"| |- |Kleinandelfingen || style="width: 30%; background-color: #d05454;"| |- |Kleinbösingen || style="width: 30%; background-color: #d05454;"| |- |Kleindietwil || style="width: 30%; background-color: #d05454;"| |- |Kleindöttingen || style="width: 30%; background-color: #d05454;"| |- |Kleine Scheidegg || style="width: 30%; background-color: #d05454;"| |- |Kleingurmels || style="width: 30%; background-color: #d05454;"| |- |Kleinlützel || style="width: 30%; background-color: #99FF99;"|Argus |- |Kleinwangen || style="width: 30%; background-color: #d05454;"| |- |Klingnau || style="width: 30%; background-color: #99FF99;"|Argus |- |Klöntal || style="width: 30%; background-color: #d05454;"| |- |Klosters || style="width: 30%; background-color: #d05454;"| |- |Klosters Dorf || style="width: 30%; background-color: #d05454;"| |- |Kloten || style="width: 30%; background-color: #d05454;"| |- |Knoblisbühl || style="width: 30%; background-color: #d05454;"| |- |Knonau || style="width: 30%; background-color: #d05454;"| |- |Knutwil || style="width: 30%; background-color: #d05454;"| |- |Koblenz || style="width: 30%; background-color: #d05454;"| |- |Kollbrunn || style="width: 30%; background-color: #d05454;"| |- |Kölliken || style="width: 30%; background-color: #99FF99;"|Argus |- |Köniz || style="width: 30%; background-color: #99FF99;"|Argus |- |Konolfingen || style="width: 30%; background-color: #d05454;"| |- |Koppigen || style="width: 30%; background-color: #d05454;"| |- |Kottwil || style="width: 30%; background-color: #d05454;"| |- |Kradolf || style="width: 30%; background-color: #d05454;"| |- |Kräiligen || style="width: 30%; background-color: #d05454;"| |- |Krattigen || style="width: 30%; background-color: #d05454;"| |- |Krauchthal || style="width: 30%; background-color: #d05454;"| |- |Kreuzlingen || style="width: 30%; background-color: #d05454;"| |- |Kriechenwil || style="width: 30%; background-color: #d05454;"| |- |Kriegstetten || style="width: 30%; background-color: #d05454;"| |- |Kriens || style="width: 30%; background-color: #d05454;"| |- |Kriessern || style="width: 30%; background-color: #d05454;"| |- |Krinau || style="width: 30%; background-color: #d05454;"| |- |Kronbühl || style="width: 30%; background-color: #d05454;"| |- |Krummenau || style="width: 30%; background-color: #d05454;"| |- |Küblis || style="width: 30%; background-color: #d05454;"| |- |Kulmerau || style="width: 30%; background-color: #d05454;"| |- |Kümmertshausen || style="width: 30%; background-color: #d05454;"| |- |Künten || style="width: 30%; background-color: #d05454;"| |- |Küsnacht ZH || style="width: 30%; background-color: #d05454;"| |- |Küssnacht am Rigi || style="width: 30%; background-color: #d05454;"| |- |Küttigen || style="width: 30%; background-color: #d05454;"| |- |Küttigkofen || style="width: 30%; background-color: #d05454;"| |- |Kyburg || style="width: 30%; background-color: #d05454;"| |- |Kyburg-Buchegg || style="width: 30%; background-color: #d05454;"| |- |L'Etivaz || style="width: 30%; background-color: #d05454;"| |- |L‘Abbaye || style="width: 30%; background-color: #d05454;"| |- |L‘Abergement || style="width: 30%; background-color: #d05454;"| |- |L‘Auberson || style="width: 30%; background-color: #d05454;"| |- |L‘Etivaz || style="width: 30%; background-color: #d05454;"| |- |L‘Isle || style="width: 30%; background-color: #d05454;"| |- |La Brévine || style="width: 30%; background-color: #d05454;"| |- |La Châtagne || style="width: 30%; background-color: #d05454;"| |- |La Chaux (Cossonay) || style="width: 30%; background-color: #d05454;"| |- |La Chaux-de-Fonds || style="width: 30%; background-color: #d05454;"| |- |La Chaux-des-Breuleux || style="width: 30%; background-color: #d05454;"| |- |La Chaux-du-Milieu || style="width: 30%; background-color: #d05454;"| |- |La Cibourg || style="width: 30%; background-color: #d05454;"| |- |La Comballaz || style="width: 30%; background-color: #d05454;"| |- |La Conversion || style="width: 30%; background-color: #d05454;"| |- |La Corbaz || style="width: 30%; background-color: #d05454;"| |- |La Coudre || style="width: 30%; background-color: #d05454;"| |- |La Côte-aux-Fées || style="width: 30%; background-color: #d05454;"| |- |La Croix (Lutry) || style="width: 30%; background-color: #d05454;"| |- |La Croix-de-Rozon || style="width: 30%; background-color: #d05454;"| |- |La Cure || style="width: 30%; background-color: #d05454;"| |- |La Ferrière || style="width: 30%; background-color: #d05454;"| |- |La Forclaz VD || style="width: 30%; background-color: #d05454;"| |- |La Fouly VS || style="width: 30%; background-color: #d05454;"| |- |La Garde || style="width: 30%; background-color: #d05454;"| |- |La Heutte || style="width: 30%; background-color: #d05454;"| |- |La Joux FR || style="width: 30%; background-color: #d05454;"| |- |La Joux-du-Plâne || style="width: 30%; background-color: #d05454;"| |- |La Lécherette || style="width: 30%; background-color: #d05454;"| |- |La Magne || style="width: 30%; background-color: #d05454;"| |- |La Montoz || style="width: 30%; background-color: #d05454;"| |- |La Neirigue || style="width: 30%; background-color: #d05454;"| |- |La Neuveville || style="width: 30%; background-color: #d05454;"| |- |La Place (Ayent) || style="width: 30%; background-color: #d05454;"| |- |La Plaine || style="width: 30%; background-color: #d05454;"| |- |La Praille || style="width: 30%; background-color: #d05454;"| |- |La Praz || style="width: 30%; background-color: #d05454;"| |- |La Punt-Chamues-ch || style="width: 30%; background-color: #d05454;"| |- |La Rippe || style="width: 30%; background-color: #d05454;"| |- |La Roche FR || style="width: 30%; background-color: #d05454;"| |- |La Rogivue || style="width: 30%; background-color: #d05454;"| |- |La Rösa || style="width: 30%; background-color: #d05454;"| |- |La Rougève || style="width: 30%; background-color: #d05454;"| |- |La Sage || style="width: 30%; background-color: #d05454;"| |- |La Sagne NE || style="width: 30%; background-color: #d05454;"| |- |La Sagne VD || style="width: 30%; background-color: #d05454;"| |- |La Sarraz || style="width: 30%; background-color: #d05454;"| |- |La Tanne || style="width: 30%; background-color: #d05454;"| |- |La Tine || style="width: 30%; background-color: #d05454;"| |- |La Tour-de-Peilz || style="width: 30%; background-color: #d05454;"| |- |La Tour-de-Trême || style="width: 30%; background-color: #d05454;"| |- |La Vernaz || style="width: 30%; background-color: #d05454;"| |- |La Verrerie || style="width: 30%; background-color: #d05454;"| |- |La Vraconnaz || style="width: 30%; background-color: #d05454;"| |- |La Vue-des-Alpes || style="width: 30%; background-color: #d05454;"| |- |Laax GR || style="width: 30%; background-color: #d05454;"| |- |Lachen AR || style="width: 30%; background-color: #d05454;"| |- |Lachen SZ || style="width: 30%; background-color: #d05454;"| |- |Laconnex || style="width: 30%; background-color: #d05454;"| |- |Ladir || style="width: 30%; background-color: #d05454;"| |- |Lajoux JU || style="width: 30%; background-color: #d05454;"| |- |Lalden || style="width: 30%; background-color: #d05454;"| |- |Lamboing || style="width: 30%; background-color: #d05454;"| |- |Lamone || style="width: 30%; background-color: #d05454;"| |- |Lampenberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Lamperswil TG || style="width: 30%; background-color: #d05454;"| |- |Lana (Evolène) || style="width: 30%; background-color: #d05454;"| |- |Landquart || style="width: 30%; background-color: #d05454;"| |- |Landschlacht || style="width: 30%; background-color: #d05454;"| |- |Langenbruck || style="width: 30%; background-color: #d05454;"| |- |Längenbühl || style="width: 30%; background-color: #d05454;"| |- |Langendorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Langenthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Langnau am Albis || style="width: 30%; background-color: #99FF99;"|Argus |- |Langnau b. Reiden || style="width: 30%; background-color: #d05454;"| |- |Langnau im Emmental || style="width: 30%; background-color: #d05454;"| |- |Langrickenbach || style="width: 30%; background-color: #d05454;"| |- |Langwies || style="width: 30%; background-color: #d05454;"| |- |Langwiesen || style="width: 30%; background-color: #d05454;"| |- |Lanterswil || style="width: 30%; background-color: #d05454;"| |- |Lantsch/Lenz || style="width: 30%; background-color: #d05454;"| |- |Lanzenhäusern || style="width: 30%; background-color: #d05454;"| |- |Lanzenneunforn || style="width: 30%; background-color: #d05454;"| |- |Largario || style="width: 30%; background-color: #d05454;"| |- |Latsch || style="width: 30%; background-color: #d05454;"| |- |Latterbach || style="width: 30%; background-color: #d05454;"| |- |Lätti || style="width: 30%; background-color: #d05454;"| |- |Lauenen b. Gstaad || style="width: 30%; background-color: #d05454;"| |- |Lauerz || style="width: 30%; background-color: #d05454;"| |- |Läufelfingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Laufen || style="width: 30%; background-color: #99FF99;"|Argus |- |Laufenburg || style="width: 30%; background-color: #99FF99;"|Argus |- |Laupen BE || style="width: 30%; background-color: #d05454;"| |- |Laupen ZH || style="width: 30%; background-color: #d05454;"| |- |Laupersdorf || style="width: 30%; background-color: #d05454;"| |- |Lauperswil || style="width: 30%; background-color: #d05454;"| |- |Laura || style="width: 30%; background-color: #d05454;"| |- |Lausanne || style="width: 30%; background-color: #d05454;"| |- |Lausen || style="width: 30%; background-color: #99FF99;"|Argus |- |Lauterbrunnen || style="width: 30%; background-color: #d05454;"| |- |Lauwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Lavertezzo || style="width: 30%; background-color: #d05454;"| |- |Lavey-les-Bains || style="width: 30%; background-color: #d05454;"| |- |Lavey-Village || style="width: 30%; background-color: #d05454;"| |- |Lavigny || style="width: 30%; background-color: #d05454;"| |- |Lavin || style="width: 30%; background-color: #d05454;"| |- |Lavorgo || style="width: 30%; background-color: #d05454;"| |- |Lax || style="width: 30%; background-color: #d05454;"| |- |Le Bémont JU || style="width: 30%; background-color: #d05454;"| |- |Le Boéchet || style="width: 30%; background-color: #d05454;"| |- |Le Brassus || style="width: 30%; background-color: #d05454;"| |- |Le Brouillet || style="width: 30%; background-color: #d05454;"| |- |Le Bry || style="width: 30%; background-color: #d05454;"| |- |Le Cerneux-Veusil || style="width: 30%; background-color: #d05454;"| |- |Le Châble VS || style="width: 30%; background-color: #d05454;"| |- |Le Château-de-Ste-Croix || style="width: 30%; background-color: #d05454;"| |- |Le Châtelard VS || style="width: 30%; background-color: #d05454;"| |- |Le Châtelard-près-Romont || style="width: 30%; background-color: #d05454;"| |- |Le Crêt-du-Locle || style="width: 30%; background-color: #d05454;"| |- |Le Crêt-près-Semsales || style="width: 30%; background-color: #d05454;"| |- |Le Fregnoley || style="width: 30%; background-color: #d05454;"| |- |Le Fuet || style="width: 30%; background-color: #d05454;"| |- |Le Grand-Saconnex || style="width: 30%; background-color: #d05454;"| |- |Le Jordil || style="width: 30%; background-color: #d05454;"| |- |Le Landeron || style="width: 30%; background-color: #d05454;"| |- |Le Lieu || style="width: 30%; background-color: #d05454;"| |- |Le Lignon || style="width: 30%; background-color: #d05454;"| |- |Le Locle || style="width: 30%; background-color: #d05454;"| |- |Le Mont-Pèlerin || style="width: 30%; background-color: #d05454;"| |- |Le Mont-sur-Lausanne || style="width: 30%; background-color: #d05454;"| |- |Le Morgnes || style="width: 30%; background-color: #d05454;"| |- |Le Mouret || style="width: 30%; background-color: #d05454;"| |- |Le Muids || style="width: 30%; background-color: #d05454;"| |- |Le Noirmont || style="width: 30%; background-color: #d05454;"| |- |Le Pâquier NE || style="width: 30%; background-color: #d05454;"| |- |Le Pâquier-Montbarry || style="width: 30%; background-color: #d05454;"| |- |Le Peuchapatte || style="width: 30%; background-color: #d05454;"| |- |Le Planchamp || style="width: 30%; background-color: #d05454;"| |- |Le Pont || style="width: 30%; background-color: #d05454;"| |- |Le Prédame || style="width: 30%; background-color: #d05454;"| |- |Le Prese || style="width: 30%; background-color: #d05454;"| |- |Le Prévoux || style="width: 30%; background-color: #d05454;"| |- |Le Sentier || style="width: 30%; background-color: #d05454;"| |- |Le Sépey || style="width: 30%; background-color: #d05454;"| |- |Le Solliat || style="width: 30%; background-color: #d05454;"| |- |Le Trétien || style="width: 30%; background-color: #d05454;"| |- |Le Vaud || style="width: 30%; background-color: #d05454;"| |- |Léchelles || style="width: 30%; background-color: #d05454;"| |- |Leggia || style="width: 30%; background-color: #d05454;"| |- |Leibstadt || style="width: 30%; background-color: #d05454;"| |- |Leimbach AG || style="width: 30%; background-color: #d05454;"| |- |Leimbach TG || style="width: 30%; background-color: #d05454;"| |- |Leimiswil || style="width: 30%; background-color: #d05454;"| |- |Leissigen || style="width: 30%; background-color: #d05454;"| |- |Lenggenwil || style="width: 30%; background-color: #d05454;"| |- |Lengnau AG || style="width: 30%; background-color: #d05454;"| |- |Lengnau BE || style="width: 30%; background-color: #d05454;"| |- |Lengwil-Oberhofen || style="width: 30%; background-color: #d05454;"| |- |Lenk im Simmental || style="width: 30%; background-color: #d05454;"| |- |Lens || style="width: 30%; background-color: #d05454;"| |- |Lentigny || style="width: 30%; background-color: #99FF99;"|Argus |- |Lenzburg || style="width: 30%; background-color: #99FF99;"|Argus |- |Lenzerheide/Lai || style="width: 30%; background-color: #d05454;"| |- |Leontica || style="width: 30%; background-color: #d05454;"| |- |Les Acacias || style="width: 30%; background-color: #d05454;"| |- |Les Agettes || style="width: 30%; background-color: #d05454;"| |- |Les Avanchets || style="width: 30%; background-color: #d05454;"| |- |Les Avants || style="width: 30%; background-color: #d05454;"| |- |Les Bayards || style="width: 30%; background-color: #d05454;"| |- |Les Bioux || style="width: 30%; background-color: #d05454;"| |- |Les Bois || style="width: 30%; background-color: #d05454;"| |- |Les Brenets || style="width: 30%; background-color: #d05454;"| |- |Les Breuleux || style="width: 30%; background-color: #d05454;"| |- |Les Charbonnières || style="width: 30%; background-color: #d05454;"| |- |Les Clées || style="width: 30%; background-color: #d05454;"| |- |Les Collons || style="width: 30%; background-color: #d05454;"| |- |Les Crosets || style="width: 30%; background-color: #d05454;"| |- |Les Cullayes || style="width: 30%; background-color: #d05454;"| |- |Les Diablerets || style="width: 30%; background-color: #d05454;"| |- |Les Ecasseys || style="width: 30%; background-color: #d05454;"| |- |Les Ecorcheresses || style="width: 30%; background-color: #d05454;"| |- |Les Emibois || style="width: 30%; background-color: #d05454;"| |- |Les Enfers || style="width: 30%; background-color: #d05454;"| |- |Les Evouettes || style="width: 30%; background-color: #d05454;"| |- |Les Frêtes || style="width: 30%; background-color: #d05454;"| |- |Les Friques || style="width: 30%; background-color: #d05454;"| |- |Les Genevez JU || style="width: 30%; background-color: #d05454;"| |- |Les Giettes || style="width: 30%; background-color: #d05454;"| |- |Les Haudères || style="width: 30%; background-color: #d05454;"| |- |Les Hauts-Geneveys || style="width: 30%; background-color: #d05454;"| |- |Les Joux-Derrière || style="width: 30%; background-color: #d05454;"| |- |Les Loges || style="width: 30%; background-color: #d05454;"| |- |Les Marécottes || style="width: 30%; background-color: #d05454;"| |- |Les Mayens-de-Sion || style="width: 30%; background-color: #d05454;"| |- |Les Monts-de-Corsier || style="width: 30%; background-color: #d05454;"| |- |Les Monts-de-Pully || style="width: 30%; background-color: #d05454;"| |- |Les Mosses || style="width: 30%; background-color: #d05454;"| |- |Les Moulins || style="width: 30%; background-color: #d05454;"| |- |Les Moulins VS || style="width: 30%; background-color: #d05454;"| |- |Les Paccots || style="width: 30%; background-color: #d05454;"| |- |Les Petits-Ponts || style="width: 30%; background-color: #d05454;"| |- |Les Places || style="width: 30%; background-color: #d05454;"| |- |Les Planchettes || style="width: 30%; background-color: #d05454;"| |- |Les Plans-sur-Bex || style="width: 30%; background-color: #d05454;"| |- |Les Pommerats || style="width: 30%; background-color: #d05454;"| |- |Les Pontins || style="width: 30%; background-color: #d05454;"| |- |Les Posses-sur-Bex || style="width: 30%; background-color: #d05454;"| |- |Les Prés-d‘Orvin || style="width: 30%; background-color: #d05454;"| |- |Les Rasses || style="width: 30%; background-color: #d05454;"| |- |Les Reussilles || style="width: 30%; background-color: #d05454;"| |- |Les Ruillères || style="width: 30%; background-color: #d05454;"| |- |Les Sagnettes || style="width: 30%; background-color: #d05454;"| |- |Les Taillères || style="width: 30%; background-color: #d05454;"| |- |Les Tavernes || style="width: 30%; background-color: #d05454;"| |- |Les Thioleyres || style="width: 30%; background-color: #d05454;"| |- |Les Valettes || style="width: 30%; background-color: #d05454;"| |- |Les Vérines || style="width: 30%; background-color: #d05454;"| |- |Les Verrières || style="width: 30%; background-color: #d05454;"| |- |Les Vieux-Prés || style="width: 30%; background-color: #d05454;"| |- |Lessoc || style="width: 30%; background-color: #d05454;"| |- |Leuggelbach || style="width: 30%; background-color: #d05454;"| |- |Leuggern || style="width: 30%; background-color: #d05454;"| |- |Leuk Stadt || style="width: 30%; background-color: #d05454;"| |- |Leukerbad || style="width: 30%; background-color: #d05454;"| |- |Leutwil || style="width: 30%; background-color: #d05454;"| |- |Leuzigen || style="width: 30%; background-color: #d05454;"| |- |Levron || style="width: 30%; background-color: #d05454;"| |- |Leysin || style="width: 30%; background-color: #d05454;"| |- |Leytron || style="width: 30%; background-color: #d05454;"| |- |Li Curt || style="width: 30%; background-color: #d05454;"| |- |Libingen || style="width: 30%; background-color: #d05454;"| |- |Lichtensteig || style="width: 30%; background-color: #d05454;"| |- |Liddes || style="width: 30%; background-color: #d05454;"| |- |Liebefeld || style="width: 30%; background-color: #99FF99;"|Argus |- |Liebistorf || style="width: 30%; background-color: #d05454;"| |- |Liedertswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Lieffrens || style="width: 30%; background-color: #d05454;"| |- |Lieli LU || style="width: 30%; background-color: #d05454;"| |- |Lienz || style="width: 30%; background-color: #d05454;"| |- |Liesberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Liesberg Dorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Liestal || style="width: 30%; background-color: #99FF99;"|Argus |- |Liez (St-Martin) || style="width: 30%; background-color: #d05454;"| |- |Ligerz || style="width: 30%; background-color: #d05454;"| |- |Lignerolle || style="width: 30%; background-color: #d05454;"| |- |Lignières || style="width: 30%; background-color: #d05454;"| |- |Ligornetto || style="width: 30%; background-color: #d05454;"| |- |Limpach || style="width: 30%; background-color: #d05454;"| |- |Lindau || style="width: 30%; background-color: #d05454;"| |- |Linden || style="width: 30%; background-color: #d05454;"| |- |Linescio || style="width: 30%; background-color: #d05454;"| |- |Linthal || style="width: 30%; background-color: #d05454;"| |- |Lipperswil || style="width: 30%; background-color: #d05454;"| |- |Lippoldswilen || style="width: 30%; background-color: #d05454;"| |- |Littau || style="width: 30%; background-color: #d05454;"| |- |Littenheid || style="width: 30%; background-color: #d05454;"| |- |Litzirüti || style="width: 30%; background-color: #d05454;"| |- |Lobsigen || style="width: 30%; background-color: #d05454;"| |- |Loc || style="width: 30%; background-color: #d05454;"| |- |Locarno || style="width: 30%; background-color: #d05454;"| |- |Loco || style="width: 30%; background-color: #d05454;"| |- |Lodano || style="width: 30%; background-color: #d05454;"| |- |Lodrino || style="width: 30%; background-color: #d05454;"| |- |Lohn GR || style="width: 30%; background-color: #d05454;"| |- |Lohn SH || style="width: 30%; background-color: #d05454;"| |- |Lohn-Ammannsegg || style="width: 30%; background-color: #d05454;"| |- |Löhningen || style="width: 30%; background-color: #d05454;"| |- |Lohnstorf || style="width: 30%; background-color: #d05454;"| |- |Lömmenschwil || style="width: 30%; background-color: #d05454;"| |- |Lommis || style="width: 30%; background-color: #d05454;"| |- |Lommiswil || style="width: 30%; background-color: #d05454;"| |- |Lonay || style="width: 30%; background-color: #d05454;"| |- |Longirod || style="width: 30%; background-color: #d05454;"| |- |Lopagno || style="width: 30%; background-color: #d05454;"| |- |Losone || style="width: 30%; background-color: #d05454;"| |- |Lossy || style="width: 30%; background-color: #d05454;"| |- |Lostallo || style="width: 30%; background-color: #d05454;"| |- |Lostorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Lottigna || style="width: 30%; background-color: #d05454;"| |- |Lotzwil || style="width: 30%; background-color: #d05454;"| |- |Lourtier || style="width: 30%; background-color: #d05454;"| |- |Lovatens || style="width: 30%; background-color: #d05454;"| |- |Lovens || style="width: 30%; background-color: #99FF99;"|Argus |- |Loveresse || style="width: 30%; background-color: #d05454;"| |- |Lü || style="width: 30%; background-color: #d05454;"| |- |Luc (Ayent) || style="width: 30%; background-color: #d05454;"| |- |Lucelle || style="width: 30%; background-color: #d05454;"| |- |Lucens || style="width: 30%; background-color: #d05454;"| |- |Lüchingen || style="width: 30%; background-color: #d05454;"| |- |Luchsingen || style="width: 30%; background-color: #d05454;"| |- |Ludiano || style="width: 30%; background-color: #d05454;"| |- |Lüen || style="width: 30%; background-color: #d05454;"| |- |Lufingen || style="width: 30%; background-color: #d05454;"| |- |Lugaggia || style="width: 30%; background-color: #d05454;"| |- |Lugano || style="width: 30%; background-color: #d05454;"| |- |Lugnez || style="width: 30%; background-color: #d05454;"| |- |Lugnorre || style="width: 30%; background-color: #d05454;"| |- |Luins || style="width: 30%; background-color: #d05454;"| |- |Lully FR || style="width: 30%; background-color: #d05454;"| |- |Lully VD || style="width: 30%; background-color: #d05454;"| |- |Lumbrein || style="width: 30%; background-color: #d05454;"| |- |Lumino || style="width: 30%; background-color: #d05454;"| |- |Lungern || style="width: 30%; background-color: #d05454;"| |- |Lupfig || style="width: 30%; background-color: #99FF99;"|Argus |- |Lupsingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Lurtigen || style="width: 30%; background-color: #d05454;"| |- |Lüscherz || style="width: 30%; background-color: #d05454;"| |- |Lussery-Villars || style="width: 30%; background-color: #d05454;"| |- |Lüsslingen || style="width: 30%; background-color: #d05454;"| |- |Lussy FR || style="width: 30%; background-color: #d05454;"| |- |Lussy-sur-Morges || style="width: 30%; background-color: #d05454;"| |- |Lustdorf || style="width: 30%; background-color: #d05454;"| |- |Lustmühle || style="width: 30%; background-color: #d05454;"| |- |Luterbach || style="width: 30%; background-color: #d05454;"| |- |Lüterkofen || style="width: 30%; background-color: #d05454;"| |- |Lüterswil || style="width: 30%; background-color: #d05454;"| |- |Luthern || style="width: 30%; background-color: #d05454;"| |- |Luthern Bad || style="width: 30%; background-color: #d05454;"| |- |Lütisburg || style="width: 30%; background-color: #d05454;"| |- |Lütisburg Station || style="width: 30%; background-color: #d05454;"| |- |Lutry || style="width: 30%; background-color: #d05454;"| |- |Lütschental || style="width: 30%; background-color: #d05454;"| |- |Lützelflüh-Goldbach || style="width: 30%; background-color: #d05454;"| |- |Lutzenberg || style="width: 30%; background-color: #d05454;"| |- |Luven || style="width: 30%; background-color: #d05454;"| |- |Luzein || style="width: 30%; background-color: #d05454;"| |- |Luzern || style="width: 30%; background-color: #d05454;"| |- |Lyss || style="width: 30%; background-color: #d05454;"| |- |Lyssach || style="width: 30%; background-color: #d05454;"| |- |Mâche || style="width: 30%; background-color: #d05454;"| |- |Madetswil || style="width: 30%; background-color: #d05454;"| |- |Madiswil || style="width: 30%; background-color: #d05454;"| |- |Madonna del Piano || style="width: 30%; background-color: #d05454;"| |- |Madrano || style="width: 30%; background-color: #d05454;"| |- |Mädris-Vermol || style="width: 30%; background-color: #d05454;"| |- |Madulain || style="width: 30%; background-color: #d05454;"| |- |Magadino || style="width: 30%; background-color: #d05454;"| |- |Magden || style="width: 30%; background-color: #99FF99;"|Argus |- |Mägenwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Maggia || style="width: 30%; background-color: #d05454;"| |- |Magglingen/Macolin || style="width: 30%; background-color: #d05454;"| |- |Magliaso || style="width: 30%; background-color: #d05454;"| |- |Maglio di Colla || style="width: 30%; background-color: #d05454;"| |- |Magnedens || style="width: 30%; background-color: #d05454;"| |- |Maienfeld || style="width: 30%; background-color: #d05454;"| |- |Mairengo || style="width: 30%; background-color: #d05454;"| |- |Maisprach || style="width: 30%; background-color: #99FF99;"|Argus |- |Maladers || style="width: 30%; background-color: #d05454;"| |- |Malans GR || style="width: 30%; background-color: #d05454;"| |- |Malans SG || style="width: 30%; background-color: #d05454;"| |- |Malapalud || style="width: 30%; background-color: #d05454;"| |- |Malix || style="width: 30%; background-color: #d05454;"| |- |Malleray || style="width: 30%; background-color: #d05454;"| |- |Maloja || style="width: 30%; background-color: #d05454;"| |- |Malters || style="width: 30%; background-color: #d05454;"| |- |Malvaglia || style="width: 30%; background-color: #d05454;"| |- |Mamishaus || style="width: 30%; background-color: #d05454;"| |- |Mammern || style="width: 30%; background-color: #d05454;"| |- |Mandach || style="width: 30%; background-color: #99FF99;"|Argus |- |Männedorf || style="width: 30%; background-color: #d05454;"| |- |Mannenbach-Salenstein || style="width: 30%; background-color: #d05454;"| |- |Mannens || style="width: 30%; background-color: #d05454;"| |- |Manno || style="width: 30%; background-color: #d05454;"| |- |Maracon || style="width: 30%; background-color: #d05454;"| |- |Marbach LU || style="width: 30%; background-color: #d05454;"| |- |Marbach SG || style="width: 30%; background-color: #d05454;"| |- |Marchissy || style="width: 30%; background-color: #d05454;"| |- |Mariastein || style="width: 30%; background-color: #99FF99;"|Argus |- |Marin-Epagnier || style="width: 30%; background-color: #d05454;"| |- |Marly || style="width: 30%; background-color: #d05454;"| |- |Marmorera || style="width: 30%; background-color: #d05454;"| |- |Marnand || style="width: 30%; background-color: #d05454;"| |- |Maroggia || style="width: 30%; background-color: #d05454;"| |- |Marolta || style="width: 30%; background-color: #d05454;"| |- |Marsens || style="width: 30%; background-color: #99FF99;"|Argus |- |Märstetten || style="width: 30%; background-color: #d05454;"| |- |Marthalen || style="width: 30%; background-color: #d05454;"| |- |Martherenges || style="width: 30%; background-color: #d05454;"| |- |Martigny || style="width: 30%; background-color: #d05454;"| |- |Martigny-Croix || style="width: 30%; background-color: #d05454;"| |- |Martina || style="width: 30%; background-color: #d05454;"| |- |Martisberg || style="width: 30%; background-color: #d05454;"| |- |Märwil || style="width: 30%; background-color: #d05454;"| |- |Maschwanden || style="width: 30%; background-color: #d05454;"| |- |Mase || style="width: 30%; background-color: #d05454;"| |- |Masein || style="width: 30%; background-color: #d05454;"| |- |Maseltrangen || style="width: 30%; background-color: #d05454;"| |- |Massagno || style="width: 30%; background-color: #d05454;"| |- |Massongex || style="width: 30%; background-color: #d05454;"| |- |Massonnens || style="width: 30%; background-color: #d05454;"| |- |Mastrils || style="width: 30%; background-color: #d05454;"| |- |Mathod || style="width: 30%; background-color: #d05454;"| |- |Mathon || style="width: 30%; background-color: #d05454;"| |- |Matran || style="width: 30%; background-color: #d05454;"| |- |Matt || style="width: 30%; background-color: #d05454;"| |- |Matten (St.Stephan) || style="width: 30%; background-color: #d05454;"| |- |Matten b. Interlaken || style="width: 30%; background-color: #d05454;"| |- |Mattstetten || style="width: 30%; background-color: #d05454;"| |- |Mattwil || style="width: 30%; background-color: #d05454;"| |- |Matzendorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Matzingen || style="width: 30%; background-color: #d05454;"| |- |Mauborget || style="width: 30%; background-color: #d05454;"| |- |Mauensee || style="width: 30%; background-color: #d05454;"| |- |Maules || style="width: 30%; background-color: #d05454;"| |- |Maur || style="width: 30%; background-color: #d05454;"| |- |Mauraz || style="width: 30%; background-color: #d05454;"| |- |Mauren TG || style="width: 30%; background-color: #d05454;"| |- |Mayens-de-Chamoson || style="width: 30%; background-color: #d05454;"| |- |Mayens-de-la-Zour || style="width: 30%; background-color: #d05454;"| |- |Mayens-de-Riddes || style="width: 30%; background-color: #d05454;"| |- |Medeglia || style="width: 30%; background-color: #d05454;"| |- |Medels || style="width: 30%; background-color: #d05454;"| |- |Meggen || style="width: 30%; background-color: #d05454;"| |- |Mehlsecken || style="width: 30%; background-color: #d05454;"| |- |Meien || style="width: 30%; background-color: #d05454;"| |- |Meienberg || style="width: 30%; background-color: #d05454;"| |- |Meienried || style="width: 30%; background-color: #d05454;"| |- |Meierskappel || style="width: 30%; background-color: #d05454;"| |- |Meikirch || style="width: 30%; background-color: #d05454;"| |- |Meilen || style="width: 30%; background-color: #d05454;"| |- |Meinier || style="width: 30%; background-color: #d05454;"| |- |Meinisberg || style="width: 30%; background-color: #d05454;"| |- |Meiringen || style="width: 30%; background-color: #d05454;"| |- |Meisterschwanden || style="width: 30%; background-color: #d05454;"| |- |Melano || style="width: 30%; background-color: #d05454;"| |- |Melchnau || style="width: 30%; background-color: #d05454;"| |- |Melchsee-Frutt || style="width: 30%; background-color: #d05454;"| |- |Melchtal || style="width: 30%; background-color: #d05454;"| |- |Melide || style="width: 30%; background-color: #d05454;"| |- |Mellikon || style="width: 30%; background-color: #99FF99;"|Argus |- |Mellingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Mels || style="width: 30%; background-color: #d05454;"| |- |Meltingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Mendrisio || style="width: 30%; background-color: #d05454;"| |- |Ménières || style="width: 30%; background-color: #d05454;"| |- |Menzberg || style="width: 30%; background-color: #d05454;"| |- |Menzengrüt || style="width: 30%; background-color: #d05454;"| |- |Menziken || style="width: 30%; background-color: #d05454;"| |- |Menzingen || style="width: 30%; background-color: #d05454;"| |- |Menznau || style="width: 30%; background-color: #d05454;"| |- |Menzonio || style="width: 30%; background-color: #d05454;"| |- |Merenschwand || style="width: 30%; background-color: #d05454;"| |- |Mergoscia || style="width: 30%; background-color: #d05454;"| |- |Meride || style="width: 30%; background-color: #d05454;"| |- |Merishausen || style="width: 30%; background-color: #d05454;"| |- |Merligen || style="width: 30%; background-color: #d05454;"| |- |Merlischachen || style="width: 30%; background-color: #d05454;"| |- |Mervelier || style="width: 30%; background-color: #d05454;"| |- |Merzligen || style="width: 30%; background-color: #d05454;"| |- |Mesocco || style="width: 30%; background-color: #d05454;"| |- |Messen || style="width: 30%; background-color: #d05454;"| |- |Mettau || style="width: 30%; background-color: #d05454;"| |- |Mettembert || style="width: 30%; background-color: #d05454;"| |- |Mettendorf TG || style="width: 30%; background-color: #d05454;"| |- |Mettlen || style="width: 30%; background-color: #d05454;"| |- |Mettmenstetten || style="width: 30%; background-color: #d05454;"| |- |Metzerlen || style="width: 30%; background-color: #99FF99;"|Argus |- |Mex VD || style="width: 30%; background-color: #d05454;"| |- |Mex VS || style="width: 30%; background-color: #d05454;"| |- |Meyriez || style="width: 30%; background-color: #d05454;"| |- |Meyrin || style="width: 30%; background-color: #d05454;"| |- |Mézery-près-Donneloye || style="width: 30%; background-color: #d05454;"| |- |Mézières FR || style="width: 30%; background-color: #d05454;"| |- |Mézières VD || style="width: 30%; background-color: #d05454;"| |- |Mezzovico || style="width: 30%; background-color: #d05454;"| |- |Middes || style="width: 30%; background-color: #d05454;"| |- |Miécourt || style="width: 30%; background-color: #d05454;"| |- |Miège || style="width: 30%; background-color: #d05454;"| |- |Mies || style="width: 30%; background-color: #d05454;"| |- |Miex || style="width: 30%; background-color: #d05454;"| |- |Miglieglia || style="width: 30%; background-color: #d05454;"| |- |Milken || style="width: 30%; background-color: #d05454;"| |- |Minusio || style="width: 30%; background-color: #d05454;"| |- |Miralago || style="width: 30%; background-color: #d05454;"| |- |Mirchel || style="width: 30%; background-color: #d05454;"| |- |Misériez (Salins) || style="width: 30%; background-color: #d05454;"| |- |Misery || style="width: 30%; background-color: #d05454;"| |- |Mission || style="width: 30%; background-color: #d05454;"| |- |Missy || style="width: 30%; background-color: #d05454;"| |- |Mitlödi || style="width: 30%; background-color: #d05454;"| |- |Mittelhäusern || style="width: 30%; background-color: #99FF99;"|Argus |- |Mittellunden || style="width: 30%; background-color: #d05454;"| |- |Mogelsberg || style="width: 30%; background-color: #d05454;"| |- |Moghegno || style="width: 30%; background-color: #d05454;"| |- |Möhlin || style="width: 30%; background-color: #99FF99;"|Argus |- |Moiry VD || style="width: 30%; background-color: #d05454;"| |- |Molare || style="width: 30%; background-color: #d05454;"| |- |Moleno || style="width: 30%; background-color: #d05454;"| |- |Moléson-sur-Gruyères || style="width: 30%; background-color: #d05454;"| |- |Molinazzo || style="width: 30%; background-color: #d05454;"| |- |Molinis || style="width: 30%; background-color: #d05454;"| |- |Mollens VD || style="width: 30%; background-color: #d05454;"| |- |Mollens VS || style="width: 30%; background-color: #d05454;"| |- |Mollie-Margot || style="width: 30%; background-color: #d05454;"| |- |Mollis || style="width: 30%; background-color: #d05454;"| |- |Molondin || style="width: 30%; background-color: #d05454;"| |- |Mols || style="width: 30%; background-color: #d05454;"| |- |Mon || style="width: 30%; background-color: #d05454;"| |- |Mönchaltorf || style="width: 30%; background-color: #d05454;"| |- |Moneto || style="width: 30%; background-color: #d05454;"| |- |Monible || style="width: 30%; background-color: #d05454;"| |- |Monnaz || style="width: 30%; background-color: #d05454;"| |- |Mont-Crosin || style="width: 30%; background-color: #d05454;"| |- |Mont-de-Buttes || style="width: 30%; background-color: #d05454;"| |- |Mont-la-Ville || style="width: 30%; background-color: #d05454;"| |- |Mont-Soleil || style="width: 30%; background-color: #d05454;"| |- |Mont-sur-Rolle || style="width: 30%; background-color: #d05454;"| |- |Mont-Tramelan || style="width: 30%; background-color: #d05454;"| |- |Montagne-Courtelary || style="width: 30%; background-color: #d05454;"| |- |Montagne-Sonvilier || style="width: 30%; background-color: #d05454;"| |- |Montagnier || style="width: 30%; background-color: #d05454;"| |- |Montagnola || style="width: 30%; background-color: #d05454;"| |- |Montagnon (Leytron) || style="width: 30%; background-color: #d05454;"| |- |Montagny-la-Ville || style="width: 30%; background-color: #d05454;"| |- |Montagny-les-Monts || style="width: 30%; background-color: #d05454;"| |- |Montagny-près-Yverdon || style="width: 30%; background-color: #d05454;"| |- |Montalchez || style="width: 30%; background-color: #d05454;"| |- |Montana || style="width: 30%; background-color: #d05454;"| |- |Montaubion-Chardonney || style="width: 30%; background-color: #d05454;"| |- |Montavon || style="width: 30%; background-color: #d05454;"| |- |Montbovon || style="width: 30%; background-color: #d05454;"| |- |Montbrelloz || style="width: 30%; background-color: #d05454;"| |- |Montcherand || style="width: 30%; background-color: #d05454;"| |- |Monte || style="width: 30%; background-color: #d05454;"| |- |Monte Carasso || style="width: 30%; background-color: #d05454;"| |- |Monteiller-Savièse || style="width: 30%; background-color: #d05454;"| |- |Montenol || style="width: 30%; background-color: #d05454;"| |- |Montet (Broye) || style="width: 30%; background-color: #d05454;"| |- |Montet (Glâne) || style="width: 30%; background-color: #d05454;"| |- |Montévraz || style="width: 30%; background-color: #d05454;"| |- |Montezillon || style="width: 30%; background-color: #d05454;"| |- |Montfaucon || style="width: 30%; background-color: #d05454;"| |- |Montfavergier || style="width: 30%; background-color: #d05454;"| |- |Mönthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Montherod || style="width: 30%; background-color: #d05454;"| |- |Monthey || style="width: 30%; background-color: #d05454;"| |- |Monti della Trinità (Locarno) || style="width: 30%; background-color: #d05454;"| |- |Montignez || style="width: 30%; background-color: #d05454;"| |- |Montlingen || style="width: 30%; background-color: #d05454;"| |- |Montmagny || style="width: 30%; background-color: #d05454;"| |- |Montmelon || style="width: 30%; background-color: #d05454;"| |- |Montmollin || style="width: 30%; background-color: #d05454;"| |- |Montpreveyres || style="width: 30%; background-color: #d05454;"| |- |Montreux || style="width: 30%; background-color: #d05454;"| |- |Montricher || style="width: 30%; background-color: #d05454;"| |- |Montsevelier || style="width: 30%; background-color: #d05454;"| |- |Moosleerau || style="width: 30%; background-color: #d05454;"| |- |Moosseedorf || style="width: 30%; background-color: #d05454;"| |- |Morbio Inferiore || style="width: 30%; background-color: #d05454;"| |- |Morbio Superiore || style="width: 30%; background-color: #d05454;"| |- |Morcles || style="width: 30%; background-color: #d05454;"| |- |Morcote || style="width: 30%; background-color: #d05454;"| |- |Mörel || style="width: 30%; background-color: #d05454;"| |- |Morens FR || style="width: 30%; background-color: #d05454;"| |- |Morgarten || style="width: 30%; background-color: #d05454;"| |- |Morges || style="width: 30%; background-color: #d05454;"| |- |Morgins || style="width: 30%; background-color: #d05454;"| |- |Mörigen || style="width: 30%; background-color: #d05454;"| |- |Möriken AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Morissen || style="width: 30%; background-color: #d05454;"| |- |Morlens || style="width: 30%; background-color: #d05454;"| |- |Morlon || style="width: 30%; background-color: #d05454;"| |- |Morrens VD || style="width: 30%; background-color: #d05454;"| |- |Morschach || style="width: 30%; background-color: #d05454;"| |- |Mörschwil || style="width: 30%; background-color: #d05454;"| |- |Mosen || style="width: 30%; background-color: #d05454;"| |- |Mosnang || style="width: 30%; background-color: #d05454;"| |- |Mosogno || style="width: 30%; background-color: #d05454;"| |- |Mossel || style="width: 30%; background-color: #d05454;"| |- |Môtier (Vully) || style="width: 30%; background-color: #d05454;"| |- |Môtiers NE || style="width: 30%; background-color: #d05454;"| |- |Mötschwil || style="width: 30%; background-color: #d05454;"| |- |Motto (Blenio) || style="width: 30%; background-color: #d05454;"| |- |Moudon || style="width: 30%; background-color: #d05454;"| |- |Moutier || style="width: 30%; background-color: #d05454;"| |- |Movelier || style="width: 30%; background-color: #d05454;"| |- |Mt Brè Lugano || style="width: 30%; background-color: #d05454;"| |- |Mugena || style="width: 30%; background-color: #d05454;"| |- |Muggio || style="width: 30%; background-color: #d05454;"| |- |Muhen || style="width: 30%; background-color: #d05454;"| |- |Mühlau || style="width: 30%; background-color: #d05454;"| |- |Mühlebach (Goms) || style="width: 30%; background-color: #d05454;"| |- |Mühleberg || style="width: 30%; background-color: #d05454;"| |- |Mühledorf BE || style="width: 30%; background-color: #d05454;"| |- |Mühledorf SO || style="width: 30%; background-color: #d05454;"| |- |Mühlehorn || style="width: 30%; background-color: #d05454;"| |- |Mühlethal || style="width: 30%; background-color: #99FF99;"|Argus |- |Mühlethurnen || style="width: 30%; background-color: #d05454;"| |- |Mühlrüti || style="width: 30%; background-color: #d05454;"| |- |Mülchi || style="width: 30%; background-color: #d05454;"| |- |Mulegns || style="width: 30%; background-color: #d05454;"| |- |Mülenen || style="width: 30%; background-color: #d05454;"| |- |Müllheim Dorf || style="width: 30%; background-color: #d05454;"| |- |Müllheim-Wigoltingen || style="width: 30%; background-color: #d05454;"| |- |Mülligen || style="width: 30%; background-color: #99FF99;"|Argus |- |Mümliswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Mumpé Medel || style="width: 30%; background-color: #d05454;"| |- |Mumpf || style="width: 30%; background-color: #d05454;"| |- |Münchenbuchsee || style="width: 30%; background-color: #d05454;"| |- |Münchenstein || style="width: 30%; background-color: #99FF99;"|Argus |- |Münchenwiler || style="width: 30%; background-color: #d05454;"| |- |Münchringen || style="width: 30%; background-color: #d05454;"| |- |Münchwilen AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Münchwilen TG || style="width: 30%; background-color: #d05454;"| |- |Mund || style="width: 30%; background-color: #d05454;"| |- |Münsingen || style="width: 30%; background-color: #d05454;"| |- |Münster VS || style="width: 30%; background-color: #d05454;"| |- |Münsterlingen || style="width: 30%; background-color: #d05454;"| |- |Muntelier || style="width: 30%; background-color: #d05454;"| |- |Müntschemier || style="width: 30%; background-color: #d05454;"| |- |Muolen || style="width: 30%; background-color: #d05454;"| |- |Muotathal || style="width: 30%; background-color: #d05454;"| |- |Mur (Vully) FR || style="width: 30%; background-color: #d05454;"| |- |Mur (Vully) VD || style="width: 30%; background-color: #d05454;"| |- |Muralto || style="width: 30%; background-color: #d05454;"| |- |Muraz (Collombey) || style="width: 30%; background-color: #d05454;"| |- |Muraz (Sierre) || style="width: 30%; background-color: #d05454;"| |- |MurgLienechtstrasse || style="width: 30%; background-color: #d05454;"| |- |Murgenthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Muri AG || style="width: 30%; background-color: #d05454;"| |- |Muri b. Bern || style="width: 30%; background-color: #d05454;"| |- |Muriaux || style="width: 30%; background-color: #d05454;"| |- |Murist || style="width: 30%; background-color: #d05454;"| |- |Mürren || style="width: 30%; background-color: #d05454;"| |- |Murten || style="width: 30%; background-color: #d05454;"| |- |Murzelen || style="width: 30%; background-color: #d05454;"| |- |Müselbach || style="width: 30%; background-color: #d05454;"| |- |Müstair || style="width: 30%; background-color: #d05454;"| |- |Müswangen || style="width: 30%; background-color: #d05454;"| |- |Mutrux || style="width: 30%; background-color: #d05454;"| |- |Mutten || style="width: 30%; background-color: #d05454;"| |- |Muttenz || style="width: 30%; background-color: #99FF99;"|Argus |- |Muzzano || style="width: 30%; background-color: #d05454;"| |- |Näfels || style="width: 30%; background-color: #d05454;"| |- |Nänikon || style="width: 30%; background-color: #d05454;"| |- |Nassen || style="width: 30%; background-color: #d05454;"| |- |Naters || style="width: 30%; background-color: #d05454;"| |- |Nax || style="width: 30%; background-color: #d05454;"| |- |Naz || style="width: 30%; background-color: #d05454;"| |- |Nebikon || style="width: 30%; background-color: #d05454;"| |- |Necker || style="width: 30%; background-color: #d05454;"| |- |Neerach || style="width: 30%; background-color: #d05454;"| |- |Neftenbach || style="width: 30%; background-color: #d05454;"| |- |Neggio || style="width: 30%; background-color: #d05454;"| |- |Neirivue || style="width: 30%; background-color: #d05454;"| |- |Némiaz (Chamoson) || style="width: 30%; background-color: #d05454;"| |- |Nennigkofen || style="width: 30%; background-color: #d05454;"| |- |Nenzlingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Neschwil || style="width: 30%; background-color: #d05454;"| |- |Nesselnbach || style="width: 30%; background-color: #d05454;"| |- |Nessental || style="width: 30%; background-color: #d05454;"| |- |Nesslau || style="width: 30%; background-color: #d05454;"| |- |Netstal || style="width: 30%; background-color: #d05454;"| |- |Neu St. Johann || style="width: 30%; background-color: #d05454;"| |- |Neuägeri || style="width: 30%; background-color: #d05454;"| |- |Neuchâtel || style="width: 30%; background-color: #d05454;"| |- |Neudorf || style="width: 30%; background-color: #d05454;"| |- |Neuendorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Neuenegg || style="width: 30%; background-color: #d05454;"| |- |Neuenhof || style="width: 30%; background-color: #d05454;"| |- |Neuenkirch || style="width: 30%; background-color: #d05454;"| |- |Neuhaus SG || style="width: 30%; background-color: #d05454;"| |- |Neuhausen am Rheinfall || style="width: 30%; background-color: #99FF99;"|Argus |- |Neuheim || style="width: 30%; background-color: #d05454;"| |- |Neukirch (Egnach) || style="width: 30%; background-color: #d05454;"| |- |Neukirch an der Thur || style="width: 30%; background-color: #d05454;"| |- |Neunkirch || style="width: 30%; background-color: #d05454;"| |- |Neuwilen || style="width: 30%; background-color: #d05454;"| |- |Neyruz FR || style="width: 30%; background-color: #99FF99;"|Argus |- |Neyruz-sur-Moudon || style="width: 30%; background-color: #d05454;"| |- |Nidau || style="width: 30%; background-color: #d05454;"| |- |Nidfurn || style="width: 30%; background-color: #d05454;"| |- |Niederbipp || style="width: 30%; background-color: #99FF99;"|Argus |- |Niederbuchsiten || style="width: 30%; background-color: #99FF99;"|Argus |- |Niederbüren || style="width: 30%; background-color: #d05454;"| |- |Niederdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Niedergampel || style="width: 30%; background-color: #d05454;"| |- |Niedergesteln || style="width: 30%; background-color: #d05454;"| |- |Niederglatt SG || style="width: 30%; background-color: #d05454;"| |- |Niederglatt ZH || style="width: 30%; background-color: #d05454;"| |- |Niedergösgen || style="width: 30%; background-color: #99FF99;"|Argus |- |Niederhasli || style="width: 30%; background-color: #d05454;"| |- |Niederhelfenschwil || style="width: 30%; background-color: #d05454;"| |- |Niederhünigen || style="width: 30%; background-color: #d05454;"| |- |Niederlenz || style="width: 30%; background-color: #99FF99;"|Argus |- |Niedermuhlern || style="width: 30%; background-color: #d05454;"| |- |Niederneunforn || style="width: 30%; background-color: #d05454;"| |- |Niederönz || style="width: 30%; background-color: #d05454;"| |- |Niederösch || style="width: 30%; background-color: #d05454;"| |- |Niederrickenbach || style="width: 30%; background-color: #d05454;"| |- |Niederried b. Kallnach || style="width: 30%; background-color: #d05454;"| |- |Niederried Interlaken || style="width: 30%; background-color: #d05454;"| |- |Niederrohrdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Niederscherli || style="width: 30%; background-color: #d05454;"| |- |Niederstetten || style="width: 30%; background-color: #d05454;"| |- |Niederstocken || style="width: 30%; background-color: #d05454;"| |- |Niederteufen || style="width: 30%; background-color: #d05454;"| |- |Niederurnen || style="width: 30%; background-color: #d05454;"| |- |Niederuzwil || style="width: 30%; background-color: #d05454;"| |- |Niederwald || style="width: 30%; background-color: #d05454;"| |- |Niederwangen b. Bern || style="width: 30%; background-color: #d05454;"| |- |Niederweningen || style="width: 30%; background-color: #d05454;"| |- |Niederwil AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Niederwil SG || style="width: 30%; background-color: #d05454;"| |- |Niederwil SO || style="width: 30%; background-color: #d05454;"| |- |Nierlet-les-Bois || style="width: 30%; background-color: #d05454;"| |- |Niesen Kulm || style="width: 30%; background-color: #d05454;"| |- |Niouc || style="width: 30%; background-color: #d05454;"| |- |Niva (Vallemaggia) || style="width: 30%; background-color: #d05454;"| |- |Nivo || style="width: 30%; background-color: #d05454;"| |- |Nods || style="width: 30%; background-color: #d05454;"| |- |Noës || style="width: 30%; background-color: #d05454;"| |- |Noflen BE || style="width: 30%; background-color: #d05454;"| |- |Nohl || style="width: 30%; background-color: #d05454;"| |- |Noiraigue || style="width: 30%; background-color: #d05454;"| |- |Noréaz || style="width: 30%; background-color: #99FF99;"|Argus |- |Nottwil || style="width: 30%; background-color: #d05454;"| |- |Novaggio || style="width: 30%; background-color: #d05454;"| |- |Novalles || style="width: 30%; background-color: #d05454;"| |- |Novazzano || style="width: 30%; background-color: #d05454;"| |- |Noville || style="width: 30%; background-color: #d05454;"| |- |Nufenen || style="width: 30%; background-color: #d05454;"| |- |Nuglar || style="width: 30%; background-color: #99FF99;"|Argus |- |Nunningen || style="width: 30%; background-color: #99FF99;"|Argus |- |Nürensdorf || style="width: 30%; background-color: #d05454;"| |- |Nussbaumen AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Nussbaumen TG || style="width: 30%; background-color: #d05454;"| |- |Nusshof || style="width: 30%; background-color: #99FF99;"|Argus |- |Nuvilly || style="width: 30%; background-color: #d05454;"| |- |Nyon || style="width: 30%; background-color: #d05454;"| |- |Obbürgen || style="width: 30%; background-color: #d05454;"| |- |Oberaach || style="width: 30%; background-color: #d05454;"| |- |Oberägeri || style="width: 30%; background-color: #d05454;"| |- |Oberarth || style="width: 30%; background-color: #d05454;"| |- |Oberbalm || style="width: 30%; background-color: #d05454;"| |- |Oberbalmberg || style="width: 30%; background-color: #d05454;"| |- |Oberbipp || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberbuchsiten || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberbüren || style="width: 30%; background-color: #d05454;"| |- |Oberburg || style="width: 30%; background-color: #d05454;"| |- |Oberbussnang || style="width: 30%; background-color: #d05454;"| |- |Oberbütschel || style="width: 30%; background-color: #d05454;"| |- |Oberdiessbach || style="width: 30%; background-color: #d05454;"| |- |Oberdorf BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberdorf NW || style="width: 30%; background-color: #d05454;"| |- |Oberdorf SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberegg || style="width: 30%; background-color: #d05454;"| |- |Oberembrach || style="width: 30%; background-color: #d05454;"| |- |Oberems || style="width: 30%; background-color: #d05454;"| |- |Oberengstringen || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberentfelden || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberflachs || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberfrittenbach || style="width: 30%; background-color: #d05454;"| |- |Obergerlafingen || style="width: 30%; background-color: #d05454;"| |- |Obergesteln || style="width: 30%; background-color: #d05454;"| |- |Oberglatt ZH || style="width: 30%; background-color: #d05454;"| |- |Obergoldbach || style="width: 30%; background-color: #d05454;"| |- |Obergösgen || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberhallau || style="width: 30%; background-color: #d05454;"| |- |Oberhasli || style="width: 30%; background-color: #d05454;"| |- |Oberhelfenschwil || style="width: 30%; background-color: #d05454;"| |- |Oberhof || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberhofen AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberhofen am Thunersee || style="width: 30%; background-color: #d05454;"| |- |Oberhünigen || style="width: 30%; background-color: #d05454;"| |- |Oberiberg || style="width: 30%; background-color: #d05454;"| |- |Oberkirch LU || style="width: 30%; background-color: #d05454;"| |- |Oberkulm || style="width: 30%; background-color: #d05454;"| |- |Oberlunkhofen || style="width: 30%; background-color: #d05454;"| |- |Obermumpf || style="width: 30%; background-color: #99FF99;"|Argus |- |Obermutten || style="width: 30%; background-color: #d05454;"| |- |Obernau || style="width: 30%; background-color: #d05454;"| |- |Oberneunforn || style="width: 30%; background-color: #d05454;"| |- |Oberönz || style="width: 30%; background-color: #d05454;"| |- |Oberösch || style="width: 30%; background-color: #d05454;"| |- |Oberramsern || style="width: 30%; background-color: #d05454;"| |- |Oberrickenbach || style="width: 30%; background-color: #d05454;"| |- |Oberried Brienz || style="width: 30%; background-color: #d05454;"| |- |Oberried FR || style="width: 30%; background-color: #d05454;"| |- |Oberrieden || style="width: 30%; background-color: #d05454;"| |- |Oberriet SG || style="width: 30%; background-color: #d05454;"| |- |Oberrindal || style="width: 30%; background-color: #d05454;"| |- |Oberrohrdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberrüti || style="width: 30%; background-color: #99FF99;"|Argus |- |Obers Friggahüs || style="width: 30%; background-color: #d05454;"| |- |Obersaxen Affeier || style="width: 30%; background-color: #d05454;"| |- |Obersaxen Giraniga || style="width: 30%; background-color: #d05454;"| |- |Obersaxen Meierhof || style="width: 30%; background-color: #d05454;"| |- |Oberschan || style="width: 30%; background-color: #d05454;"| |- |Oberschrot || style="width: 30%; background-color: #d05454;"| |- |Oberstammheim || style="width: 30%; background-color: #d05454;"| |- |Obersteckholz || style="width: 30%; background-color: #d05454;"| |- |Oberstetten || style="width: 30%; background-color: #d05454;"| |- |Oberstocken || style="width: 30%; background-color: #d05454;"| |- |Oberterzen || style="width: 30%; background-color: #d05454;"| |- |Oberthal || style="width: 30%; background-color: #d05454;"| |- |Oberurnen || style="width: 30%; background-color: #d05454;"| |- |Oberuzwil || style="width: 30%; background-color: #d05454;"| |- |Oberwald || style="width: 30%; background-color: #d05454;"| |- |Oberwangen b. Bern || style="width: 30%; background-color: #d05454;"| |- |Oberwangen TG || style="width: 30%; background-color: #d05454;"| |- |Oberweningen || style="width: 30%; background-color: #d05454;"| |- |Oberwil (Dägerlen) || style="width: 30%; background-color: #d05454;"| |- |Oberwil b. Büren || style="width: 30%; background-color: #d05454;"| |- |Oberwil b. Zug || style="width: 30%; background-color: #d05454;"| |- |Oberwil BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Oberwil im Simmental || style="width: 30%; background-color: #d05454;"| |- |Oberwil-Lieli || style="width: 30%; background-color: #d05454;"| |- |Obfelden || style="width: 30%; background-color: #d05454;"| |- |Obstalden || style="width: 30%; background-color: #d05454;"| |- |Ochlenberg || style="width: 30%; background-color: #d05454;"| |- |Ocourt || style="width: 30%; background-color: #d05454;"| |- |Odogno || style="width: 30%; background-color: #d05454;"| |- |Oekingen || style="width: 30%; background-color: #d05454;"| |- |Oensingen || style="width: 30%; background-color: #d05454;"| |- |Oerlingen || style="width: 30%; background-color: #d05454;"| |- |Oeschenbach || style="width: 30%; background-color: #d05454;"| |- |Oeschgen || style="width: 30%; background-color: #d05454;"| |- |Oeschseite || style="width: 30%; background-color: #d05454;"| |- |Oetwil am See || style="width: 30%; background-color: #d05454;"| |- |Oetwil an der Limmat || style="width: 30%; background-color: #99FF99;"|Argus |- |Oey || style="width: 30%; background-color: #d05454;"| |- |Oftringen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ogens || style="width: 30%; background-color: #d05454;"| |- |Oggio || style="width: 30%; background-color: #d05454;"| |- |Ohmstal || style="width: 30%; background-color: #d05454;"| |- |Oleyres || style="width: 30%; background-color: #d05454;"| |- |Olivone || style="width: 30%; background-color: #d05454;"| |- |Ollon VD || style="width: 30%; background-color: #d05454;"| |- |Ollon VS || style="width: 30%; background-color: #d05454;"| |- |Olsberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Olten || style="width: 30%; background-color: #d05454;"| |- |Oltingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Onex || style="width: 30%; background-color: #d05454;"| |- |Onnens FR || style="width: 30%; background-color: #99FF99;"|Argus |- |Onnens VD || style="width: 30%; background-color: #d05454;"| |- |Onsernone || style="width: 30%; background-color: #d05454;"| |- |Opfershofen TG || style="width: 30%; background-color: #d05454;"| |- |Opfertshofen SH || style="width: 30%; background-color: #d05454;"| |- |Opfikon || style="width: 30%; background-color: #d05454;"| |- |Oppens || style="width: 30%; background-color: #d05454;"| |- |Oppikon || style="width: 30%; background-color: #d05454;"| |- |Oppligen || style="width: 30%; background-color: #d05454;"| |- |Orbe || style="width: 30%; background-color: #d05454;"| |- |Orges || style="width: 30%; background-color: #d05454;"| |- |Orient || style="width: 30%; background-color: #d05454;"| |- |Origlio || style="width: 30%; background-color: #d05454;"| |- |Ormalingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ormône (Savièse) || style="width: 30%; background-color: #d05454;"| |- |Orny || style="width: 30%; background-color: #d05454;"| |- |Oron-la-Ville || style="width: 30%; background-color: #d05454;"| |- |Oron-le-Châtel || style="width: 30%; background-color: #d05454;"| |- |Orpund || style="width: 30%; background-color: #d05454;"| |- |Orselina || style="width: 30%; background-color: #d05454;"| |- |Orsières || style="width: 30%; background-color: #d05454;"| |- |Orsonnens || style="width: 30%; background-color: #99FF99;"|Argus |- |Ortschwaben || style="width: 30%; background-color: #d05454;"| |- |Orvin || style="width: 30%; background-color: #d05454;"| |- |Orzens || style="width: 30%; background-color: #d05454;"| |- |Oschwand || style="width: 30%; background-color: #d05454;"| |- |Osco || style="width: 30%; background-color: #d05454;"| |- |Osogna || style="width: 30%; background-color: #d05454;"| |- |Ospizio Bernina || style="width: 30%; background-color: #d05454;"| |- |Ossingen || style="width: 30%; background-color: #d05454;"| |- |Osterfingen || style="width: 30%; background-color: #d05454;"| |- |Ostermundigen || style="width: 30%; background-color: #d05454;"| |- |Otelfingen || style="width: 30%; background-color: #d05454;"| |- |Othmarsingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ottenbach || style="width: 30%; background-color: #d05454;"| |- |Ottikon (Gossau ZH) || style="width: 30%; background-color: #d05454;"| |- |Ottikon b. Kemptthal || style="width: 30%; background-color: #d05454;"| |- |Ottoberg || style="width: 30%; background-color: #d05454;"| |- |Oulens-sous-Echallens || style="width: 30%; background-color: #d05454;"| |- |Oulens-sur-Lucens || style="width: 30%; background-color: #d05454;"| |- |Ovronnaz || style="width: 30%; background-color: #d05454;"| |- |Pagig || style="width: 30%; background-color: #d05454;"| |- |Pailly || style="width: 30%; background-color: #d05454;"| |- |Palagnedra || style="width: 30%; background-color: #d05454;"| |- |Palasuit (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Palézieux || style="width: 30%; background-color: #d05454;"| |- |Palézieux-Village || style="width: 30%; background-color: #d05454;"| |- |Pambio-Noranco || style="width: 30%; background-color: #d05454;"| |- |Pampigny || style="width: 30%; background-color: #d05454;"| |- |Panex || style="width: 30%; background-color: #d05454;"| |- |Pany || style="width: 30%; background-color: #d05454;"| |- |Paradiso || style="width: 30%; background-color: #d05454;"| |- |Parpan || style="width: 30%; background-color: #d05454;"| |- |Parsonz || style="width: 30%; background-color: #d05454;"| |- |Paspels || style="width: 30%; background-color: #d05454;"| |- |Passugg-Araschgen || style="width: 30%; background-color: #d05454;"| |- |Paudex || style="width: 30%; background-color: #d05454;"| |- |Payerne || style="width: 30%; background-color: #d05454;"| |- |Pazzallo || style="width: 30%; background-color: #d05454;"| |- |Peccia || style="width: 30%; background-color: #d05454;"| |- |Pedrinate || style="width: 30%; background-color: #d05454;"| |- |Peist || style="width: 30%; background-color: #d05454;"| |- |Peney-le-Jorat || style="width: 30%; background-color: #d05454;"| |- |Pensier || style="width: 30%; background-color: #d05454;"| |- |Penthalaz || style="width: 30%; background-color: #d05454;"| |- |Penthaz || style="width: 30%; background-color: #d05454;"| |- |Penthéréaz || style="width: 30%; background-color: #d05454;"| |- |Perlen || style="width: 30%; background-color: #d05454;"| |- |Perly || style="width: 30%; background-color: #d05454;"| |- |Perrefitte || style="width: 30%; background-color: #d05454;"| |- |Perroy || style="width: 30%; background-color: #d05454;"| |- |Personico || style="width: 30%; background-color: #d05454;"| |- |Péry || style="width: 30%; background-color: #d05454;"| |- |Peseux || style="width: 30%; background-color: #d05454;"| |- |Petit Vichères || style="width: 30%; background-color: #d05454;"| |- |Petit-Lancy || style="width: 30%; background-color: #d05454;"| |- |Petit-Martel || style="width: 30%; background-color: #d05454;"| |- |Peyres-Possens || style="width: 30%; background-color: #d05454;"| |- |Pfäfers || style="width: 30%; background-color: #d05454;"| |- |Pfaffhausen || style="width: 30%; background-color: #d05454;"| |- |Pfäffikon SZ || style="width: 30%; background-color: #d05454;"| |- |Pfäffikon ZH || style="width: 30%; background-color: #d05454;"| |- |Pfaffnau || style="width: 30%; background-color: #d05454;"| |- |Pfeffikon LU || style="width: 30%; background-color: #d05454;"| |- |Pfeffingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Pfungen || style="width: 30%; background-color: #d05454;"| |- |Pfyn || style="width: 30%; background-color: #d05454;"| |- |Piandera Paese || style="width: 30%; background-color: #d05454;"| |- |Pianezzo || style="width: 30%; background-color: #d05454;"| |- |Piano di Peccia || style="width: 30%; background-color: #d05454;"| |- |Piazzogna || style="width: 30%; background-color: #d05454;"| |- |Pierrafortscha || style="width: 30%; background-color: #d05454;"| |- |Pieterlen || style="width: 30%; background-color: #d05454;"| |- |Pignia || style="width: 30%; background-color: #d05454;"| |- |Pigniu || style="width: 30%; background-color: #99FF99;"|Argus |- |Pilatus Kulm || style="width: 30%; background-color: #d05454;"| |- |Piotta || style="width: 30%; background-color: #d05454;"| |- |Pitasch || style="width: 30%; background-color: #d05454;"| |- |Pizy || style="width: 30%; background-color: #d05454;"| |- |Plaffeien || style="width: 30%; background-color: #d05454;"| |- |Plagne || style="width: 30%; background-color: #d05454;"| |- |Plan-les-Ouates || style="width: 30%; background-color: #d05454;"| |- |Plasselb || style="width: 30%; background-color: #d05454;"| |- |Platta || style="width: 30%; background-color: #d05454;"| |- |Platz || style="width: 30%; background-color: #d05454;"| |- |Plaun da Lej || style="width: 30%; background-color: #d05454;"| |- |Pleigne || style="width: 30%; background-color: #d05454;"| |- |Pleujouse || style="width: 30%; background-color: #d05454;"| |- |Plons || style="width: 30%; background-color: #d05454;"| |- |Pohlern || style="width: 30%; background-color: #d05454;"| |- |Poliez-le-Grand || style="width: 30%; background-color: #d05454;"| |- |Poliez-Pittet || style="width: 30%; background-color: #d05454;"| |- |Pollegio || style="width: 30%; background-color: #d05454;"| |- |Pompaples || style="width: 30%; background-color: #d05454;"| |- |Pomy || style="width: 30%; background-color: #d05454;"| |- |Pont (Veveyse) || style="width: 30%; background-color: #d05454;"| |- |Pont-de-la-Morge || style="width: 30%; background-color: #d05454;"| |- |Pont-la-Ville || style="width: 30%; background-color: #d05454;"| |- |Ponte Capriasca || style="width: 30%; background-color: #d05454;"| |- |Ponte Cremenaga || style="width: 30%; background-color: #d05454;"| |- |Ponte Tresa || style="width: 30%; background-color: #d05454;"| |- |Pontenet || style="width: 30%; background-color: #d05454;"| |- |Ponthaux || style="width: 30%; background-color: #99FF99;"|Argus |- |Ponto Valentino || style="width: 30%; background-color: #d05454;"| |- |Pontresina || style="width: 30%; background-color: #d05454;"| |- |Ponts-de-Martel || style="width: 30%; background-color: #d05454;"| |- |Porrentruy || style="width: 30%; background-color: #d05454;"| |- |Porsel || style="width: 30%; background-color: #d05454;"| |- |Port || style="width: 30%; background-color: #d05454;"| |- |Port-Valais || style="width: 30%; background-color: #d05454;"| |- |Portalban || style="width: 30%; background-color: #d05454;"| |- |Portein || style="width: 30%; background-color: #d05454;"| |- |Porto Ronco || style="width: 30%; background-color: #d05454;"| |- |Porza || style="width: 30%; background-color: #d05454;"| |- |Posat || style="width: 30%; background-color: #d05454;"| |- |Poschiavo || style="width: 30%; background-color: #d05454;"| |- |Posieux || style="width: 30%; background-color: #d05454;"| |- |Praden || style="width: 30%; background-color: #d05454;"| |- |Pragg-Jenaz || style="width: 30%; background-color: #d05454;"| |- |Prahins || style="width: 30%; background-color: #d05454;"| |- |Prangins || style="width: 30%; background-color: #d05454;"| |- |Praratoud || style="width: 30%; background-color: #d05454;"| |- |Prarreyer || style="width: 30%; background-color: #d05454;"| |- |Prato (Leventina) || style="width: 30%; background-color: #d05454;"| |- |Prato-Sornico || style="width: 30%; background-color: #d05454;"| |- |Pratteln || style="width: 30%; background-color: #99FF99;"|Argus |- |Pratval || style="width: 30%; background-color: #d05454;"| |- |Pravidondaz || style="width: 30%; background-color: #d05454;"| |- |Präz || style="width: 30%; background-color: #d05454;"| |- |Praz (Vully) || style="width: 30%; background-color: #d05454;"| |- |Praz-de-Fort || style="width: 30%; background-color: #d05454;"| |- |Preda || style="width: 30%; background-color: #d05454;"| |- |Pregassona || style="width: 30%; background-color: #d05454;"| |- |Prêles || style="width: 30%; background-color: #d05454;"| |- |Premier || style="width: 30%; background-color: #d05454;"| |- |Preonzo || style="width: 30%; background-color: #d05454;"| |- |Presinge || style="width: 30%; background-color: #d05454;"| |- |Préverenges || style="width: 30%; background-color: #d05454;"| |- |Prévondavaux || style="width: 30%; background-color: #d05454;"| |- |Prévonloup || style="width: 30%; background-color: #d05454;"| |- |Prez-vers-Noréaz || style="width: 30%; background-color: #d05454;"| |- |Prez-vers-Siviriez || style="width: 30%; background-color: #d05454;"| |- |Prilly || style="width: 30%; background-color: #d05454;"| |- |Pringy || style="width: 30%; background-color: #d05454;"| |- |Produit (Leytron) || style="width: 30%; background-color: #d05454;"| |- |Progens || style="width: 30%; background-color: #d05454;"| |- |Promasens || style="width: 30%; background-color: #d05454;"| |- |Promontogno || style="width: 30%; background-color: #d05454;"| |- |Prosito || style="width: 30%; background-color: #d05454;"| |- |Provence || style="width: 30%; background-color: #d05454;"| |- |Prugiasco || style="width: 30%; background-color: #d05454;"| |- |Pugerna || style="width: 30%; background-color: #d05454;"| |- |Puidoux || style="width: 30%; background-color: #d05454;"| |- |Pully || style="width: 30%; background-color: #d05454;"| |- |Puplinge || style="width: 30%; background-color: #d05454;"| |- |Pura || style="width: 30%; background-color: #d05454;"| |- |Purasca || style="width: 30%; background-color: #d05454;"| |- |Pusserein || style="width: 30%; background-color: #d05454;"| |- |Putz || style="width: 30%; background-color: #d05454;"| |- |Quarten || style="width: 30%; background-color: #d05454;"| |- |Quartino || style="width: 30%; background-color: #d05454;"| |- |Quinten || style="width: 30%; background-color: #d05454;"| |- |Quinto || style="width: 30%; background-color: #d05454;"| |- |Rabius || style="width: 30%; background-color: #d05454;"| |- |Radelfingen || style="width: 30%; background-color: #d05454;"| |- |Rafz || style="width: 30%; background-color: #d05454;"| |- |Rain || style="width: 30%; background-color: #d05454;"| |- |Ramersberg || style="width: 30%; background-color: #d05454;"| |- |Rämismühle || style="width: 30%; background-color: #d05454;"| |- |Ramiswil || style="width: 30%; background-color: #d05454;"| |- |Ramlinsburg || style="width: 30%; background-color: #d05454;"| |- |Ramosch || style="width: 30%; background-color: #d05454;"| |- |Ramsei || style="width: 30%; background-color: #d05454;"| |- |Ramsen || style="width: 30%; background-color: #d05454;"| |- |Rancate || style="width: 30%; background-color: #d05454;"| |- |Rances || style="width: 30%; background-color: #d05454;"| |- |Randa || style="width: 30%; background-color: #d05454;"| |- |Randogne || style="width: 30%; background-color: #d05454;"| |- |Ranflüh || style="width: 30%; background-color: #d05454;"| |- |Ranzo || style="width: 30%; background-color: #d05454;"| |- |Raperswilen || style="width: 30%; background-color: #d05454;"| |- |Rapperswil BE || style="width: 30%; background-color: #d05454;"| |- |Rapperswil-Jona || style="width: 30%; background-color: #d05454;"| |- |Raron || style="width: 30%; background-color: #d05454;"| |- |Rasa || style="width: 30%; background-color: #d05454;"| |- |Räterschen || style="width: 30%; background-color: #d05454;"| |- |Ravoire || style="width: 30%; background-color: #d05454;"| |- |Realp || style="width: 30%; background-color: #d05454;"| |- |Realta || style="width: 30%; background-color: #d05454;"| |- |Rebeuvelier || style="width: 30%; background-color: #d05454;"| |- |Rebévelier || style="width: 30%; background-color: #d05454;"| |- |Rebstein || style="width: 30%; background-color: #d05454;"| |- |Recherswil || style="width: 30%; background-color: #d05454;"| |- |Rechthalten || style="width: 30%; background-color: #d05454;"| |- |Réchy || style="width: 30%; background-color: #d05454;"| |- |Reckingen VS || style="width: 30%; background-color: #d05454;"| |- |Réclère || style="width: 30%; background-color: #d05454;"| |- |Reconvilier || style="width: 30%; background-color: #d05454;"| |- |Regensberg || style="width: 30%; background-color: #d05454;"| |- |Regensdorf || style="width: 30%; background-color: #d05454;"| |- |Rehetobel || style="width: 30%; background-color: #d05454;"| |- |Reichenbach im Kandertal || style="width: 30%; background-color: #d05454;"| |- |Reichenburg || style="width: 30%; background-color: #d05454;"| |- |Reiden || style="width: 30%; background-color: #d05454;"| |- |Reidermoos || style="width: 30%; background-color: #d05454;"| |- |Reigoldswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Reinach AG || style="width: 30%; background-color: #d05454;"| |- |Reinach BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Reisiswil || style="width: 30%; background-color: #d05454;"| |- |Reitnau || style="width: 30%; background-color: #d05454;"| |- |Rekingen AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Remaufens || style="width: 30%; background-color: #d05454;"| |- |Remetschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Remigen || style="width: 30%; background-color: #99FF99;"|Argus |- |Renan BE || style="width: 30%; background-color: #d05454;"| |- |Renens VD || style="width: 30%; background-color: #d05454;"| |- |Rengg || style="width: 30%; background-color: #d05454;"| |- |Rennaz || style="width: 30%; background-color: #d05454;"| |- |Retschwil || style="width: 30%; background-color: #d05454;"| |- |Reussbühl || style="width: 30%; background-color: #d05454;"| |- |Reute AR || style="width: 30%; background-color: #d05454;"| |- |Reutigen || style="width: 30%; background-color: #d05454;"| |- |Reutlingen || style="width: 30%; background-color: #d05454;"| |- |Reverolle || style="width: 30%; background-color: #d05454;"| |- |Rhäzüns || style="width: 30%; background-color: #d05454;"| |- |Rheinau || style="width: 30%; background-color: #d05454;"| |- |Rheineck || style="width: 30%; background-color: #d05454;"| |- |Rheinfelden || style="width: 30%; background-color: #99FF99;"|Argus |- |Rheinklingen || style="width: 30%; background-color: #d05454;"| |- |Rheinsulz || style="width: 30%; background-color: #99FF99;"|Argus |- |Riaz || style="width: 30%; background-color: #99FF99;"|Argus |- |Riazzino || style="width: 30%; background-color: #d05454;"| |- |Richenthal || style="width: 30%; background-color: #d05454;"| |- |Richigen || style="width: 30%; background-color: #d05454;"| |- |Richterswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Ricken SG || style="width: 30%; background-color: #d05454;"| |- |Rickenbach b. Wil || style="width: 30%; background-color: #d05454;"| |- |Rickenbach BL || style="width: 30%; background-color: #99FF99;"|Argus |- |Rickenbach LU || style="width: 30%; background-color: #d05454;"| |- |Rickenbach SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Rickenbach Sulz || style="width: 30%; background-color: #d05454;"| |- |Rickenbach b. Schwyz || style="width: 30%; background-color: #d05454;"| |- |Rickenbach ZH || style="width: 30%; background-color: #99FF99;"|Argus |- |Ricketwil (Winterthur) || style="width: 30%; background-color: #d05454;"| |- |Riddes || style="width: 30%; background-color: #d05454;"| |- |Ried (Frutigen) || style="width: 30%; background-color: #d05454;"| |- |Ried (Muotathal) || style="width: 30%; background-color: #d05454;"| |- |Ried b. Kerzers || style="width: 30%; background-color: #d05454;"| |- |Ried-Brig || style="width: 30%; background-color: #d05454;"| |- |Ried-Mörel || style="width: 30%; background-color: #d05454;"| |- |Rieden AG || style="width: 30%; background-color: #d05454;"| |- |Rieden SG || style="width: 30%; background-color: #d05454;"| |- |Riederalp || style="width: 30%; background-color: #d05454;"| |- |Riedern || style="width: 30%; background-color: #d05454;"| |- |Riedholz || style="width: 30%; background-color: #99FF99;"|Argus |- |Riedikon || style="width: 30%; background-color: #d05454;"| |- |Riedstätt || style="width: 30%; background-color: #d05454;"| |- |Riedt b. Erlen || style="width: 30%; background-color: #d05454;"| |- |Riedtwil || style="width: 30%; background-color: #d05454;"| |- |Riehen || style="width: 30%; background-color: #99FF99;"|Argus |- |Riein || style="width: 30%; background-color: #d05454;"| |- |Riemenstalden || style="width: 30%; background-color: #d05454;"| |- |Riet (Neftenbach) || style="width: 30%; background-color: #d05454;"| |- |Rietheim || style="width: 30%; background-color: #99FF99;"|Argus |- |Riex || style="width: 30%; background-color: #d05454;"| |- |Riffenmatt || style="width: 30%; background-color: #d05454;"| |- |Rifferswil || style="width: 30%; background-color: #d05454;"| |- |Riggisberg || style="width: 30%; background-color: #d05454;"| |- |Rigi Kaltbad || style="width: 30%; background-color: #d05454;"| |- |Rigi Klösterli || style="width: 30%; background-color: #d05454;"| |- |Rigi Kulm || style="width: 30%; background-color: #d05454;"| |- |Rigi Scheidegg || style="width: 30%; background-color: #d05454;"| |- |Rigi Staffel || style="width: 30%; background-color: #d05454;"| |- |Riken AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Rikon im Tösstal || style="width: 30%; background-color: #d05454;"| |- |Ringgenberg BE || style="width: 30%; background-color: #d05454;"| |- |Ringoldswil || style="width: 30%; background-color: #d05454;"| |- |Riniken || style="width: 30%; background-color: #99FF99;"|Argus |- |Riom || style="width: 30%; background-color: #d05454;"| |- |Risch || style="width: 30%; background-color: #d05454;"| |- |Ritzingen || style="width: 30%; background-color: #d05454;"| |- |Riva San Vitale || style="width: 30%; background-color: #d05454;"| |- |Rivaz || style="width: 30%; background-color: #d05454;"| |- |Rive Haute (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Riveo || style="width: 30%; background-color: #d05454;"| |- |Rivera || style="width: 30%; background-color: #d05454;"| |- |Rizenbach || style="width: 30%; background-color: #d05454;"| |- |Robasacco || style="width: 30%; background-color: #d05454;"| |- |Roche VD || style="width: 30%; background-color: #d05454;"| |- |Roche-d‘Or || style="width: 30%; background-color: #d05454;"| |- |Rochefort || style="width: 30%; background-color: #d05454;"| |- |Roches BE || style="width: 30%; background-color: #d05454;"| |- |Rocourt || style="width: 30%; background-color: #d05454;"| |- |Rodels || style="width: 30%; background-color: #d05454;"| |- |Rodersdorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Rodi-Fiesso || style="width: 30%; background-color: #d05454;"| |- |Roggenburg || style="width: 30%; background-color: #99FF99;"|Argus |- |Roggliswil || style="width: 30%; background-color: #d05454;"| |- |Roggwil BE || style="width: 30%; background-color: #99FF99;"|Argus |- |Roggwil TG || style="width: 30%; background-color: #d05454;"| |- |Rohr b. Olten || style="width: 30%; background-color: #99FF99;"|Argus |- |Rohrbach || style="width: 30%; background-color: #d05454;"| |- |Rohrbachgraben || style="width: 30%; background-color: #d05454;"| |- |Rohrmatt || style="width: 30%; background-color: #d05454;"| |- |Rolle || style="width: 30%; background-color: #d05454;"| |- |Romainmôtier || style="width: 30%; background-color: #d05454;"| |- |Romairon || style="width: 30%; background-color: #d05454;"| |- |Romanel-sur-Lausanne || style="width: 30%; background-color: #d05454;"| |- |Romanel-sur-Morges || style="width: 30%; background-color: #d05454;"| |- |Romanens || style="width: 30%; background-color: #d05454;"| |- |Romanshorn || style="width: 30%; background-color: #d05454;"| |- |Rombach || style="width: 30%; background-color: #99FF99;"|Argus |- |Römerswil LU || style="width: 30%; background-color: #d05454;"| |- |Romont BE || style="width: 30%; background-color: #d05454;"| |- |Romont FR || style="width: 30%; background-color: #d05454;"| |- |Romoos || style="width: 30%; background-color: #d05454;"| |- |Rona || style="width: 30%; background-color: #d05454;"| |- |Ronco sopra Ascona || style="width: 30%; background-color: #d05454;"| |- |Rongellen || style="width: 30%; background-color: #d05454;"| |- |Root || style="width: 30%; background-color: #d05454;"| |- |Root Längenbold || style="width: 30%; background-color: #d05454;"| |- |Ropraz || style="width: 30%; background-color: #d05454;"| |- |Rorbas || style="width: 30%; background-color: #d05454;"| |- |Rorschach || style="width: 30%; background-color: #d05454;"| |- |Rorschacherberg || style="width: 30%; background-color: #d05454;"| |- |Röschenz || style="width: 30%; background-color: #99FF99;"|Argus |- |Rosé || style="width: 30%; background-color: #d05454;"| |- |Rosenlaui || style="width: 30%; background-color: #d05454;"| |- |Rossa || style="width: 30%; background-color: #d05454;"| |- |Rossemaison || style="width: 30%; background-color: #d05454;"| |- |Rossenges || style="width: 30%; background-color: #d05454;"| |- |Rossens FR || style="width: 30%; background-color: #99FF99;"|Argus |- |Rossens VD || style="width: 30%; background-color: #d05454;"| |- |Rosshäusern || style="width: 30%; background-color: #d05454;"| |- |Rossinière || style="width: 30%; background-color: #d05454;"| |- |Rossrüti || style="width: 30%; background-color: #d05454;"| |- |Rossura || style="width: 30%; background-color: #d05454;"| |- |Rosswald || style="width: 30%; background-color: #d05454;"| |- |Röthenbach Herzogenbuchsee || style="width: 30%; background-color: #d05454;"| |- |Röthenbach im Emmental || style="width: 30%; background-color: #d05454;"| |- |Rothenbrunnen || style="width: 30%; background-color: #d05454;"| |- |Rothenburg || style="width: 30%; background-color: #99FF99;"|Argus |- |Rothenfluh || style="width: 30%; background-color: #99FF99;"|Argus |- |Rothenhausen || style="width: 30%; background-color: #d05454;"| |- |Rothenthurm || style="width: 30%; background-color: #d05454;"| |- |Rothrist || style="width: 30%; background-color: #99FF99;"|Argus |- |Rothwald || style="width: 30%; background-color: #d05454;"| |- |Rotkreuz || style="width: 30%; background-color: #d05454;"| |- |Rottenschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Rougemont || style="width: 30%; background-color: #d05454;"| |- |Roumaz (Savièse) || style="width: 30%; background-color: #d05454;"| |- |Roveredo GR || style="width: 30%; background-color: #d05454;"| |- |Roveredo TI || style="width: 30%; background-color: #d05454;"| |- |Rovio || style="width: 30%; background-color: #d05454;"| |- |Rovray || style="width: 30%; background-color: #d05454;"| |- |Rubigen || style="width: 30%; background-color: #d05454;"| |- |Rüderswil || style="width: 30%; background-color: #d05454;"| |- |Rüdlingen || style="width: 30%; background-color: #d05454;"| |- |Rudolfingen || style="width: 30%; background-color: #d05454;"| |- |Rudolfstetten || style="width: 30%; background-color: #99FF99;"|Argus |- |Rüdtligen || style="width: 30%; background-color: #d05454;"| |- |Rue || style="width: 30%; background-color: #d05454;"| |- |Rüedisbach || style="width: 30%; background-color: #d05454;"| |- |Rüeggisberg || style="width: 30%; background-color: #d05454;"| |- |Rüegsau || style="width: 30%; background-color: #d05454;"| |- |Rüegsauschachen || style="width: 30%; background-color: #d05454;"| |- |Rüegsbach || style="width: 30%; background-color: #d05454;"| |- |Rueras || style="width: 30%; background-color: #d05454;"| |- |Rüeterswil || style="width: 30%; background-color: #d05454;"| |- |Rueun || style="width: 30%; background-color: #d05454;"| |- |Rueyres || style="width: 30%; background-color: #d05454;"| |- |Rueyres-les-Prés || style="width: 30%; background-color: #d05454;"| |- |Rueyres-St-Laurent || style="width: 30%; background-color: #99FF99;"|Argus |- |Rueyres-Treyfayes || style="width: 30%; background-color: #d05454;"| |- |Rüfenach AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Rüfenacht BE || style="width: 30%; background-color: #d05454;"| |- |Rufi || style="width: 30%; background-color: #d05454;"| |- |Rumendingen || style="width: 30%; background-color: #d05454;"| |- |Rümikon AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Rumisberg || style="width: 30%; background-color: #d05454;"| |- |Rümlang || style="width: 30%; background-color: #d05454;"| |- |Rümligen || style="width: 30%; background-color: #d05454;"| |- |Rümlingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Rünenberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Rupperswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Ruppoldsried || style="width: 30%; background-color: #d05454;"| |- |Rüschegg Gambach || style="width: 30%; background-color: #d05454;"| |- |Rüschegg Heubach || style="width: 30%; background-color: #d05454;"| |- |Ruschein || style="width: 30%; background-color: #d05454;"| |- |Rüschlikon || style="width: 30%; background-color: #d05454;"| |- |Russikon || style="width: 30%; background-color: #d05454;"| |- |Russin || style="width: 30%; background-color: #d05454;"| |- |Russo || style="width: 30%; background-color: #d05454;"| |- |Russy || style="width: 30%; background-color: #d05454;"| |- |Ruswil || style="width: 30%; background-color: #d05454;"| |- |Rüthi (Rheintal) || style="width: 30%; background-color: #d05454;"| |- |Rüti b. Büren || style="width: 30%; background-color: #d05454;"| |- |Rüti b. Lyssach || style="width: 30%; background-color: #d05454;"| |- |Rüti b. Riggisberg || style="width: 30%; background-color: #d05454;"| |- |Rüti GL || style="width: 30%; background-color: #d05454;"| |- |Rüti ZH || style="width: 30%; background-color: #d05454;"| |- |Rütihof || style="width: 30%; background-color: #99FF99;"|Argus |- |Rütli || style="width: 30%; background-color: #d05454;"| |- |Rütschelen || style="width: 30%; background-color: #d05454;"| |- |Rutschwil (Dägerlen) || style="width: 30%; background-color: #d05454;"| |- |Rüttenen || style="width: 30%; background-color: #d05454;"| |- |Ruvigliana || style="width: 30%; background-color: #d05454;"| |- |S-chanf || style="width: 30%; background-color: #d05454;"| |- |S. Antonino || style="width: 30%; background-color: #d05454;"| |- |S. Antonio (Val Morobbia) || style="width: 30%; background-color: #d05454;"| |- |S. Benedetg || style="width: 30%; background-color: #d05454;"| |- |S. Bernardino || style="width: 30%; background-color: #d05454;"| |- |S. Carlo || style="width: 30%; background-color: #d05454;"| |- |S. Carlo (Poschiavo) || style="width: 30%; background-color: #d05454;"| |- |S. Gottardo || style="width: 30%; background-color: #d05454;"| |- |S. Nazzaro || style="width: 30%; background-color: #d05454;"| |- |S. Pietro || style="width: 30%; background-color: #d05454;"| |- |S. Vittore || style="width: 30%; background-color: #d05454;"| |- |Saanen || style="width: 30%; background-color: #d05454;"| |- |Saanenmöser || style="width: 30%; background-color: #d05454;"| |- |Saas im Prättigau || style="width: 30%; background-color: #d05454;"| |- |Saas-Almagell || style="width: 30%; background-color: #d05454;"| |- |Saas-Balen || style="width: 30%; background-color: #d05454;"| |- |Saas-Fee || style="width: 30%; background-color: #d05454;"| |- |Saas-Grund || style="width: 30%; background-color: #d05454;"| |- |Sachseln || style="width: 30%; background-color: #d05454;"| |- |Saclentz (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Safenwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Safien Platz || style="width: 30%; background-color: #d05454;"| |- |Safnern || style="width: 30%; background-color: #d05454;"| |- |Sagno || style="width: 30%; background-color: #d05454;"| |- |Sagogn || style="width: 30%; background-color: #d05454;"| |- |Saicourt || style="width: 30%; background-color: #d05454;"| |- |Saignelégier || style="width: 30%; background-color: #d05454;"| |- |Saillon || style="width: 30%; background-color: #d05454;"| |- |Saint-Germain || style="width: 30%; background-color: #d05454;"| |- |Saint-Martin FR || style="width: 30%; background-color: #d05454;"| |- |Saint-Légier-La Chiésaz || style="width: 30%; background-color: #d05454;"| |- |Saint-Romain || style="width: 30%; background-color: #d05454;"| |- |Sala Capriasca || style="width: 30%; background-color: #d05454;"| |- |Saland || style="width: 30%; background-color: #d05454;"| |- |Salavaux || style="width: 30%; background-color: #d05454;"| |- |Salenstein || style="width: 30%; background-color: #d05454;"| |- |Sâles (Gruyère) || style="width: 30%; background-color: #d05454;"| |- |Salez || style="width: 30%; background-color: #d05454;"| |- |Salgesch || style="width: 30%; background-color: #d05454;"| |- |Salins || style="width: 30%; background-color: #d05454;"| |- |Salmsach || style="width: 30%; background-color: #d05454;"| |- |Salorino || style="width: 30%; background-color: #d05454;"| |- |Salouf || style="width: 30%; background-color: #d05454;"| |- |Salvan || style="width: 30%; background-color: #d05454;"| |- |Salvenach || style="width: 30%; background-color: #d05454;"| |- |Samedan || style="width: 30%; background-color: #d05454;"| |- |Samnaun Dorf || style="width: 30%; background-color: #d05454;"| |- |Samnaun-Compatsch || style="width: 30%; background-color: #d05454;"| |- |Samstagern || style="width: 30%; background-color: #99FF99;"|Argus |- |Sangernboden || style="width: 30%; background-color: #d05454;"| |- |Sargans || style="width: 30%; background-color: #d05454;"| |- |Säriswil || style="width: 30%; background-color: #d05454;"| |- |Sarmenstorf || style="width: 30%; background-color: #d05454;"| |- |Sarn || style="width: 30%; background-color: #d05454;"| |- |Sarnen || style="width: 30%; background-color: #d05454;"| |- |Sarreyer || style="width: 30%; background-color: #d05454;"| |- |Sarzens || style="width: 30%; background-color: #d05454;"| |- |Sassel || style="width: 30%; background-color: #d05454;"| |- |Satigny || style="width: 30%; background-color: #d05454;"| |- |Sattel || style="width: 30%; background-color: #d05454;"| |- |Saubraz || style="width: 30%; background-color: #d05454;"| |- |Saulcy || style="width: 30%; background-color: #d05454;"| |- |Saules || style="width: 30%; background-color: #d05454;"| |- |Saules BE || style="width: 30%; background-color: #d05454;"| |- |Savagnier || style="width: 30%; background-color: #d05454;"| |- |Savièse || style="width: 30%; background-color: #d05454;"| |- |Savigny || style="width: 30%; background-color: #d05454;"| |- |Savognin || style="width: 30%; background-color: #d05454;"| |- |Savosa || style="width: 30%; background-color: #d05454;"| |- |Sax || style="width: 30%; background-color: #d05454;"| |- |Saxeten || style="width: 30%; background-color: #d05454;"| |- |Saxon || style="width: 30%; background-color: #d05454;"| |- |Saxonne (Ayent) || style="width: 30%; background-color: #d05454;"| |- |Says || style="width: 30%; background-color: #d05454;"| |- |Scareglia || style="width: 30%; background-color: #d05454;"| |- |Schachen b. Herisau || style="width: 30%; background-color: #d05454;"| |- |Schachen b. Reute || style="width: 30%; background-color: #d05454;"| |- |Schachen LU || style="width: 30%; background-color: #d05454;"| |- |Schaffhausen || style="width: 30%; background-color: #99FF99;"|Argus |- |Schafhausen im Emmental || style="width: 30%; background-color: #d05454;"| |- |Schafisheim || style="width: 30%; background-color: #99FF99;"|Argus |- |Schalunen || style="width: 30%; background-color: #d05454;"| |- |Schangnau || style="width: 30%; background-color: #d05454;"| |- |Schänis || style="width: 30%; background-color: #d05454;"| |- |Scharans || style="width: 30%; background-color: #d05454;"| |- |Scharnachtal || style="width: 30%; background-color: #d05454;"| |- |Schattdorf || style="width: 30%; background-color: #d05454;"| |- |Schattenhalb || style="width: 30%; background-color: #d05454;"| |- |Schatzalp (Davos) || style="width: 30%; background-color: #d05454;"| |- |Scheid || style="width: 30%; background-color: #d05454;"| |- |Schelten || style="width: 30%; background-color: #d05454;"| |- |Schenkon || style="width: 30%; background-color: #d05454;"| |- |Scherz || style="width: 30%; background-color: #99FF99;"|Argus |- |Scherzingen || style="width: 30%; background-color: #d05454;"| |- |Scheunen || style="width: 30%; background-color: #d05454;"| |- |Scheuren || style="width: 30%; background-color: #d05454;"| |- |Schiers || style="width: 30%; background-color: #d05454;"| |- |Schindellegi || style="width: 30%; background-color: #d05454;"| |- |Schinznach Bad || style="width: 30%; background-color: #99FF99;"|Argus |- |Schinznach Dorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Schlans || style="width: 30%; background-color: #d05454;"| |- |Schlatt b. Winterthur || style="width: 30%; background-color: #d05454;"| |- |Schlatt TG || style="width: 30%; background-color: #d05454;"| |- |Schlattingen || style="width: 30%; background-color: #d05454;"| |- |Schleinikon || style="width: 30%; background-color: #d05454;"| |- |Schleitheim || style="width: 30%; background-color: #d05454;"| |- |Schlierbach || style="width: 30%; background-color: #d05454;"| |- |Schlieren || style="width: 30%; background-color: #99FF99;"|Argus |- |Schliern b. Köniz || style="width: 30%; background-color: #99FF99;"|Argus |- |Schlossrued || style="width: 30%; background-color: #d05454;"| |- |Schlosswil || style="width: 30%; background-color: #d05454;"| |- |Schluein || style="width: 30%; background-color: #d05454;"| |- |Schmerikon || style="width: 30%; background-color: #d05454;"| |- |Schmidigen-Mühleweg || style="width: 30%; background-color: #d05454;"| |- |Schmidrüti || style="width: 30%; background-color: #d05454;"| |- |Schmidshof || style="width: 30%; background-color: #d05454;"| |- |Schmiedrued || style="width: 30%; background-color: #d05454;"| |- |Schmitten (Albula) || style="width: 30%; background-color: #d05454;"| |- |Schmitten FR || style="width: 30%; background-color: #d05454;"| |- |Schnaus || style="width: 30%; background-color: #d05454;"| |- |Schneisingen || style="width: 30%; background-color: #d05454;"| |- |Schnottwil || style="width: 30%; background-color: #d05454;"| |- |Schocherswil || style="width: 30%; background-color: #d05454;"| |- |Schöfflisdorf || style="width: 30%; background-color: #d05454;"| |- |Schöftland || style="width: 30%; background-color: #d05454;"| |- |Schönenbaumgarten || style="width: 30%; background-color: #d05454;"| |- |Schönenberg TG || style="width: 30%; background-color: #d05454;"| |- |Schönenberg ZH || style="width: 30%; background-color: #d05454;"| |- |Schönenbuch || style="width: 30%; background-color: #99FF99;"|Argus |- |Schönengrund || style="width: 30%; background-color: #d05454;"| |- |Schönenwerd || style="width: 30%; background-color: #99FF99;"|Argus |- |Schongau || style="width: 30%; background-color: #d05454;"| |- |Schönholzerswilen || style="width: 30%; background-color: #d05454;"| |- |Schönried || style="width: 30%; background-color: #d05454;"| |- |Schötz || style="width: 30%; background-color: #d05454;"| |- |Schübelbach || style="width: 30%; background-color: #d05454;"| |- |Schuders || style="width: 30%; background-color: #d05454;"| |- |Schüpbach || style="width: 30%; background-color: #d05454;"| |- |Schupfart || style="width: 30%; background-color: #99FF99;"|Argus |- |Schüpfen || style="width: 30%; background-color: #d05454;"| |- |Schüpfheim || style="width: 30%; background-color: #d05454;"| |- |Schwaderloch || style="width: 30%; background-color: #99FF99;"|Argus |- |Schwadernau || style="width: 30%; background-color: #d05454;"| |- |Schwanden GL || style="width: 30%; background-color: #d05454;"| |- |Schwanden im Emmental || style="width: 30%; background-color: #d05454;"| |- |Schwanden (Sigriswil) || style="width: 30%; background-color: #d05454;"| |- |Schwanden-Brienz || style="width: 30%; background-color: #d05454;"| |- |Schwändi GL || style="width: 30%; background-color: #d05454;"| |- |Schwarzenbach BE || style="width: 30%; background-color: #d05454;"| |- |Schwarzenbach LU || style="width: 30%; background-color: #d05454;"| |- |Schwarzenbach SG || style="width: 30%; background-color: #d05454;"| |- |Schwarzenberg LU || style="width: 30%; background-color: #d05454;"| |- |Schwarzenburg || style="width: 30%; background-color: #d05454;"| |- |Schwarzenegg || style="width: 30%; background-color: #d05454;"| |- |Schwarzhäusern || style="width: 30%; background-color: #d05454;"| |- |Schwarzsee || style="width: 30%; background-color: #d05454;"| |- |Schweizersholz || style="width: 30%; background-color: #d05454;"| |- |Schwellbrunn || style="width: 30%; background-color: #d05454;"| |- |Schwende || style="width: 30%; background-color: #d05454;"| |- |Schwenden im Diemtigtal || style="width: 30%; background-color: #d05454;"| |- |Schwendi || style="width: 30%; background-color: #d05454;"| |- |Schwendibach || style="width: 30%; background-color: #d05454;"| |- |Schwerzenbach || style="width: 30%; background-color: #d05454;"| |- |Schwyz || style="width: 30%; background-color: #d05454;"| |- |Sciernes-d‘Albeuve || style="width: 30%; background-color: #d05454;"| |- |Scudellate || style="width: 30%; background-color: #d05454;"| |- |Scuol || style="width: 30%; background-color: #d05454;"| |- |Sédeilles || style="width: 30%; background-color: #d05454;"| |- |Sedrun || style="width: 30%; background-color: #d05454;"| |- |Seeberg || style="width: 30%; background-color: #d05454;"| |- |Seedorf BE || style="width: 30%; background-color: #d05454;"| |- |Seedorf UR || style="width: 30%; background-color: #d05454;"| |- |Seehof || style="width: 30%; background-color: #d05454;"| |- |Seelisberg || style="width: 30%; background-color: #d05454;"| |- |Seengen || style="width: 30%; background-color: #d05454;"| |- |Seewen SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Seewen SZ || style="width: 30%; background-color: #d05454;"| |- |Seewil || style="width: 30%; background-color: #d05454;"| |- |Seewis Dorf || style="width: 30%; background-color: #d05454;"| |- |Seewis-Pardisla || style="width: 30%; background-color: #d05454;"| |- |Seewis-Schmitten || style="width: 30%; background-color: #d05454;"| |- |Seftigen || style="width: 30%; background-color: #d05454;"| |- |Segnas || style="width: 30%; background-color: #d05454;"| |- |Seigneux || style="width: 30%; background-color: #d05454;"| |- |Seiry || style="width: 30%; background-color: #d05454;"| |- |Seleute || style="width: 30%; background-color: #d05454;"| |- |Selkingen || style="width: 30%; background-color: #d05454;"| |- |Selma || style="width: 30%; background-color: #d05454;"| |- |Seltisberg || style="width: 30%; background-color: #99FF99;"|Argus |- |Selzach || style="width: 30%; background-color: #99FF99;"|Argus |- |Sembrancher || style="width: 30%; background-color: #d05454;"| |- |Sementina || style="width: 30%; background-color: #d05454;"| |- |Semione || style="width: 30%; background-color: #d05454;"| |- |Sempach || style="width: 30%; background-color: #d05454;"| |- |Sempach Station || style="width: 30%; background-color: #d05454;"| |- |Semsales || style="width: 30%; background-color: #d05454;"| |- |Senarclens || style="width: 30%; background-color: #d05454;"| |- |Senèdes || style="width: 30%; background-color: #d05454;"| |- |Sennhof (Winterthur) || style="width: 30%; background-color: #d05454;"| |- |Sennwald || style="width: 30%; background-color: #d05454;"| |- |Sent || style="width: 30%; background-color: #d05454;"| |- |Seon || style="width: 30%; background-color: #d05454;"| |- |Séprais || style="width: 30%; background-color: #d05454;"| |- |Sergey || style="width: 30%; background-color: #d05454;"| |- |Serneus || style="width: 30%; background-color: #d05454;"| |- |Serneus Station || style="width: 30%; background-color: #d05454;"| |- |Serpiano || style="width: 30%; background-color: #d05454;"| |- |Servion || style="width: 30%; background-color: #d05454;"| |- |Seseglio || style="width: 30%; background-color: #d05454;"| |- |Sessa || style="width: 30%; background-color: #d05454;"| |- |Seuzach || style="width: 30%; background-color: #d05454;"| |- |Sévaz || style="width: 30%; background-color: #d05454;"| |- |Sevelen || style="width: 30%; background-color: #d05454;"| |- |Sévery || style="width: 30%; background-color: #d05454;"| |- |Sevgein || style="width: 30%; background-color: #d05454;"| |- |Sfazù || style="width: 30%; background-color: #d05454;"| |- |Siat || style="width: 30%; background-color: #d05454;"| |- |Siblingen || style="width: 30%; background-color: #d05454;"| |- |Siebnen || style="width: 30%; background-color: #d05454;"| |- |Siegershausen || style="width: 30%; background-color: #d05454;"| |- |Sierre || style="width: 30%; background-color: #d05454;"| |- |Siggenthal Station || style="width: 30%; background-color: #99FF99;"|Argus |- |Sigigen || style="width: 30%; background-color: #d05454;"| |- |Sigirino || style="width: 30%; background-color: #d05454;"| |- |Siglistorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Signau || style="width: 30%; background-color: #d05454;"| |- |Signèse || style="width: 30%; background-color: #d05454;"| |- |Signôra || style="width: 30%; background-color: #d05454;"| |- |Signy || style="width: 30%; background-color: #d05454;"| |- |Sigriswil || style="width: 30%; background-color: #d05454;"| |- |Sihlbrugg || style="width: 30%; background-color: #d05454;"| |- |Sihlbrugg Station || style="width: 30%; background-color: #d05454;"| |- |Sihlwald || style="width: 30%; background-color: #d05454;"| |- |Silenen || style="width: 30%; background-color: #d05454;"| |- |Sils im Domleschg || style="width: 30%; background-color: #d05454;"| |- |Sils/Segl Baselgia || style="width: 30%; background-color: #d05454;"| |- |Sils/Segl Maria || style="width: 30%; background-color: #d05454;"| |- |Silvaplana || style="width: 30%; background-color: #d05454;"| |- |Silvaplana-Surlej || style="width: 30%; background-color: #d05454;"| |- |Simplon Dorf || style="width: 30%; background-color: #d05454;"| |- |Simplon Hospiz || style="width: 30%; background-color: #d05454;"| |- |Sins || style="width: 30%; background-color: #d05454;"| |- |Sion || style="width: 30%; background-color: #d05454;"| |- |Sirnach || style="width: 30%; background-color: #d05454;"| |- |Siselen BE || style="width: 30%; background-color: #d05454;"| |- |Sisikon || style="width: 30%; background-color: #d05454;"| |- |Sissach || style="width: 30%; background-color: #99FF99;"|Argus |- |Sisseln AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Sitterdorf || style="width: 30%; background-color: #d05454;"| |- |Siviez (Nendaz) || style="width: 30%; background-color: #d05454;"| |- |Siviriez || style="width: 30%; background-color: #d05454;"| |- |Soazza || style="width: 30%; background-color: #d05454;"| |- |Sobrio || style="width: 30%; background-color: #d05454;"| |- |Soglio || style="width: 30%; background-color: #d05454;"| |- |Solduno || style="width: 30%; background-color: #d05454;"| |- |Solothurn || style="width: 30%; background-color: #99FF99;"|Argus |- |Somazzo || style="width: 30%; background-color: #d05454;"| |- |Someo || style="width: 30%; background-color: #d05454;"| |- |Sommentier || style="width: 30%; background-color: #d05454;"| |- |Sommeri || style="width: 30%; background-color: #d05454;"| |- |Sonceboz-Sombeval || style="width: 30%; background-color: #d05454;"| |- |Sonnental || style="width: 30%; background-color: #d05454;"| |- |Sonogno || style="width: 30%; background-color: #d05454;"| |- |Sonterswil || style="width: 30%; background-color: #d05454;"| |- |Sonvico || style="width: 30%; background-color: #d05454;"| |- |Sonvilier || style="width: 30%; background-color: #d05454;"| |- |Sool || style="width: 30%; background-color: #d05454;"| |- |Soral || style="width: 30%; background-color: #d05454;"| |- |Sörenberg || style="width: 30%; background-color: #d05454;"| |- |Sorengo || style="width: 30%; background-color: #d05454;"| |- |Sorens || style="width: 30%; background-color: #99FF99;"|Argus |- |Sornetan || style="width: 30%; background-color: #d05454;"| |- |Sorvilier || style="width: 30%; background-color: #d05454;"| |- |Sottens || style="width: 30%; background-color: #d05454;"| |- |Soubey || style="width: 30%; background-color: #d05454;"| |- |Souboz || style="width: 30%; background-color: #d05454;"| |- |Soulce || style="width: 30%; background-color: #d05454;"| |- |Soyhières || style="width: 30%; background-color: #d05454;"| |- |Speicher || style="width: 30%; background-color: #d05454;"| |- |Speicherschwendi || style="width: 30%; background-color: #d05454;"| |- |Spiegel b. Bern || style="width: 30%; background-color: #99FF99;"|Argus |- |Spiez || style="width: 30%; background-color: #d05454;"| |- |Spiezwiler || style="width: 30%; background-color: #d05454;"| |- |Spiringen || style="width: 30%; background-color: #d05454;"| |- |Splügen || style="width: 30%; background-color: #d05454;"| |- |Spreitenbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Spruga || style="width: 30%; background-color: #d05454;"| |- |St-Aubin FR || style="width: 30%; background-color: #d05454;"| |- |St-Aubin-Sauges || style="width: 30%; background-color: #d05454;"| |- |St-Barthélemy VD || style="width: 30%; background-color: #d05454;"| |- |St-Blaise || style="width: 30%; background-color: #d05454;"| |- |St-Brais || style="width: 30%; background-color: #d05454;"| |- |St-Cergue || style="width: 30%; background-color: #d05454;"| |- |St-Cierges || style="width: 30%; background-color: #d05454;"| |- |St-George || style="width: 30%; background-color: #d05454;"| |- |St-Gingolph || style="width: 30%; background-color: #d05454;"| |- |St-Imier || style="width: 30%; background-color: #d05454;"| |- |St-Jean VS || style="width: 30%; background-color: #d05454;"| |- |St-Léonard || style="width: 30%; background-color: #d05454;"| |- |St-Livres || style="width: 30%; background-color: #d05454;"| |- |St-Luc || style="width: 30%; background-color: #d05454;"| |- |St-Martin FR || style="width: 30%; background-color: #d05454;"| |- |St-Martin VS || style="width: 30%; background-color: #d05454;"| |- |St-Maurice || style="width: 30%; background-color: #d05454;"| |- |St-Oyens || style="width: 30%; background-color: #d05454;"| |- |St-Pierre-Clages || style="width: 30%; background-color: #d05454;"| |- |St-Prex || style="width: 30%; background-color: #d05454;"| |- |St-Saphorin (Lavaux) || style="width: 30%; background-color: #d05454;"| |- |St-Saphorin-sur-Morges || style="width: 30%; background-color: #d05454;"| |- |St-Séverin || style="width: 30%; background-color: #d05454;"| |- |St-Sulpice NE || style="width: 30%; background-color: #d05454;"| |- |St-Sulpice VD || style="width: 30%; background-color: #d05454;"| |- |St-Triphon || style="width: 30%; background-color: #d05454;"| |- |St-Ursanne || style="width: 30%; background-color: #d05454;"| |- |St. Antoni || style="width: 30%; background-color: #d05454;"| |- |St. Antönien || style="width: 30%; background-color: #d05454;"| |- |St. Erhard || style="width: 30%; background-color: #d05454;"| |- |St. Gallen || style="width: 30%; background-color: #d05454;"| |- |St. Gallenkappel || style="width: 30%; background-color: #d05454;"| |- |St. German || style="width: 30%; background-color: #d05454;"| |- |St. Margarethen TG || style="width: 30%; background-color: #d05454;"| |- |St. Margrethen SG || style="width: 30%; background-color: #d05454;"| |- |St. Margrethenberg || style="width: 30%; background-color: #d05454;"| |- |St. Martin (Lugnez) || style="width: 30%; background-color: #d05454;"| |- |St. Moritz || style="width: 30%; background-color: #d05454;"| |- |St. Niklaus VS || style="width: 30%; background-color: #d05454;"| |- |St. Niklausen LU || style="width: 30%; background-color: #d05454;"| |- |St. Niklausen OW || style="width: 30%; background-color: #d05454;"| |- |St. Pantaleon || style="width: 30%; background-color: #99FF99;"|Argus |- |St. Pelagiberg || style="width: 30%; background-color: #d05454;"| |- |St. Peter || style="width: 30%; background-color: #d05454;"| |- |St. Peterzell || style="width: 30%; background-color: #d05454;"| |- |St. Silvester || style="width: 30%; background-color: #d05454;"| |- |St. Stephan || style="width: 30%; background-color: #d05454;"| |- |St. Urban || style="width: 30%; background-color: #d05454;"| |- |St. Ursen || style="width: 30%; background-color: #d05454;"| |- |Sta. Maria || style="width: 30%; background-color: #d05454;"| |- |Sta. Maria Val Müstair || style="width: 30%; background-color: #d05454;"| |- |Staad SG || style="width: 30%; background-color: #d05454;"| |- |Stabio || style="width: 30%; background-color: #d05454;"| |- |Stachen || style="width: 30%; background-color: #d05454;"| |- |Stadel (Winterthur) || style="width: 30%; background-color: #d05454;"| |- |Stadel b. Niederglatt || style="width: 30%; background-color: #d05454;"| |- |Stäfa || style="width: 30%; background-color: #d05454;"| |- |Staffelbach || style="width: 30%; background-color: #d05454;"| |- |Stalden (Sarnen) || style="width: 30%; background-color: #d05454;"| |- |Stalden VS || style="width: 30%; background-color: #d05454;"| |- |Staldenried || style="width: 30%; background-color: #d05454;"| |- |Stallikon || style="width: 30%; background-color: #d05454;"| |- |Stampa || style="width: 30%; background-color: #d05454;"| |- |Stans || style="width: 30%; background-color: #d05454;"| |- |Stansstad || style="width: 30%; background-color: #d05454;"| |- |Starrkirch-Wil || style="width: 30%; background-color: #99FF99;"|Argus |- |Staufen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ste-Croix || style="width: 30%; background-color: #d05454;"| |- |Stechelberg || style="width: 30%; background-color: #d05454;"| |- |Steckborn || style="width: 30%; background-color: #d05454;"| |- |Steffisburg || style="width: 30%; background-color: #d05454;"| |- |Steg im Tösstal || style="width: 30%; background-color: #d05454;"| |- |Steg VS || style="width: 30%; background-color: #d05454;"| |- |Stehrenberg || style="width: 30%; background-color: #d05454;"| |- |Stein AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Stein am Rhein || style="width: 30%; background-color: #d05454;"| |- |Stein AR || style="width: 30%; background-color: #d05454;"| |- |Stein SG || style="width: 30%; background-color: #d05454;"| |- |Steinach || style="width: 30%; background-color: #d05454;"| |- |Steinebrunn || style="width: 30%; background-color: #d05454;"| |- |Steinen || style="width: 30%; background-color: #d05454;"| |- |Steinerberg || style="width: 30%; background-color: #d05454;"| |- |Steinhaus || style="width: 30%; background-color: #d05454;"| |- |Steinhausen || style="width: 30%; background-color: #d05454;"| |- |Steinhof SO || style="width: 30%; background-color: #d05454;"| |- |Steinhuserberg || style="width: 30%; background-color: #d05454;"| |- |Steinmaur || style="width: 30%; background-color: #d05454;"| |- |Stels || style="width: 30%; background-color: #d05454;"| |- |Sternenberg || style="width: 30%; background-color: #d05454;"| |- |Stetten AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Stetten SH || style="width: 30%; background-color: #d05454;"| |- |Stettfurt || style="width: 30%; background-color: #d05454;"| |- |Stettlen || style="width: 30%; background-color: #d05454;"| |- |Stierva || style="width: 30%; background-color: #d05454;"| |- |Stilli || style="width: 30%; background-color: #99FF99;"|Argus |- |Stoos SZ || style="width: 30%; background-color: #d05454;"| |- |Strada || style="width: 30%; background-color: #d05454;"| |- |Strengelbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Strohwilen || style="width: 30%; background-color: #d05454;"| |- |Studen BE || style="width: 30%; background-color: #d05454;"| |- |Studen SZ || style="width: 30%; background-color: #d05454;"| |- |Stugl/Stuls || style="width: 30%; background-color: #d05454;"| |- |Stüsslingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Suberg || style="width: 30%; background-color: #d05454;"| |- |Subingen || style="width: 30%; background-color: #d05454;"| |- |Suchy || style="width: 30%; background-color: #d05454;"| |- |Süderen || style="width: 30%; background-color: #d05454;"| |- |Suen (St-Martin) || style="width: 30%; background-color: #d05454;"| |- |Sufers || style="width: 30%; background-color: #d05454;"| |- |Sugiez || style="width: 30%; background-color: #d05454;"| |- |Sugnens || style="width: 30%; background-color: #d05454;"| |- |Suhr || style="width: 30%; background-color: #d05454;"| |- |Sulgen || style="width: 30%; background-color: #d05454;"| |- |Sullens || style="width: 30%; background-color: #d05454;"| |- |Sulz AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Sulz LU || style="width: 30%; background-color: #d05454;"| |- |Sulzbach || style="width: 30%; background-color: #d05454;"| |- |Sumiswald || style="width: 30%; background-color: #d05454;"| |- |Summaprada || style="width: 30%; background-color: #d05454;"| |- |Sumvitg || style="width: 30%; background-color: #d05454;"| |- |Sundlauenen || style="width: 30%; background-color: #d05454;"| |- |Sünikon || style="width: 30%; background-color: #d05454;"| |- |Sur || style="width: 30%; background-color: #d05454;"| |- |Surava || style="width: 30%; background-color: #d05454;"| |- |Surcasti || style="width: 30%; background-color: #d05454;"| |- |Surcuolm || style="width: 30%; background-color: #d05454;"| |- |Surin || style="width: 30%; background-color: #d05454;"| |- |Surpierre || style="width: 30%; background-color: #d05454;"| |- |Surrein || style="width: 30%; background-color: #d05454;"| |- |Sursee || style="width: 30%; background-color: #d05454;"| |- |Suscévaz || style="width: 30%; background-color: #d05454;"| |- |Susch || style="width: 30%; background-color: #d05454;"| |- |Susten || style="width: 30%; background-color: #d05454;"| |- |Sutz || style="width: 30%; background-color: #d05454;"| |- |Syens || style="width: 30%; background-color: #d05454;"| |- |Tafers || style="width: 30%; background-color: #d05454;"| |- |Tagelswangen || style="width: 30%; background-color: #d05454;"| |- |Tägerig || style="width: 30%; background-color: #d05454;"| |- |Tägerschen || style="width: 30%; background-color: #d05454;"| |- |Tägertschi || style="width: 30%; background-color: #d05454;"| |- |Tägerwilen || style="width: 30%; background-color: #d05454;"| |- |Tamins || style="width: 30%; background-color: #d05454;"| |- |Tann || style="width: 30%; background-color: #d05454;"| |- |Tannay || style="width: 30%; background-color: #d05454;"| |- |Tarasp || style="width: 30%; background-color: #d05454;"| |- |Tartar || style="width: 30%; background-color: #d05454;"| |- |Tartegnin || style="width: 30%; background-color: #d05454;"| |- |Täsch || style="width: 30%; background-color: #d05454;"| |- |Tatroz || style="width: 30%; background-color: #d05454;"| |- |Täuffelen || style="width: 30%; background-color: #d05454;"| |- |Tavanasa || style="width: 30%; background-color: #d05454;"| |- |Tavannes || style="width: 30%; background-color: #d05454;"| |- |Taverne || style="width: 30%; background-color: #d05454;"| |- |Tecknau || style="width: 30%; background-color: #99FF99;"|Argus |- |Tegerfelden || style="width: 30%; background-color: #d05454;"| |- |Tegna || style="width: 30%; background-color: #d05454;"| |- |Tenero || style="width: 30%; background-color: #d05454;"| |- |Tenna || style="width: 30%; background-color: #d05454;"| |- |Tenniken || style="width: 30%; background-color: #99FF99;"|Argus |- |Tennwil || style="width: 30%; background-color: #d05454;"| |- |Tentlingen || style="width: 30%; background-color: #d05454;"| |- |Termen || style="width: 30%; background-color: #d05454;"| |- |Termine || style="width: 30%; background-color: #d05454;"| |- |Territet || style="width: 30%; background-color: #d05454;"| |- |Tersnaus || style="width: 30%; background-color: #d05454;"| |- |Tesserete || style="width: 30%; background-color: #d05454;"| |- |Teufen AR || style="width: 30%; background-color: #d05454;"| |- |Teufen ZH || style="width: 30%; background-color: #d05454;"| |- |Teufenthal AG || style="width: 30%; background-color: #d05454;"| |- |Teuffenthal b. Thun || style="width: 30%; background-color: #d05454;"| |- |Thal || style="width: 30%; background-color: #d05454;"| |- |Thalheim AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Thalheim an der Thur || style="width: 30%; background-color: #d05454;"| |- |Thalkirch || style="width: 30%; background-color: #d05454;"| |- |Thalwil || style="width: 30%; background-color: #d05454;"| |- |Thayngen || style="width: 30%; background-color: #d05454;"| |- |Theilingen || style="width: 30%; background-color: #d05454;"| |- |Therwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Thielle || style="width: 30%; background-color: #d05454;"| |- |Thielle-Wavre || style="width: 30%; background-color: #d05454;"| |- |Thierachern || style="width: 30%; background-color: #d05454;"| |- |Thierrens || style="width: 30%; background-color: #d05454;"| |- |Thônex || style="width: 30%; background-color: #d05454;"| |- |Thörigen || style="width: 30%; background-color: #d05454;"| |- |Thörishaus || style="width: 30%; background-color: #d05454;"| |- |Thun || style="width: 30%; background-color: #99FF99;"|Argus |- |Thundorf || style="width: 30%; background-color: #d05454;"| |- |Thunstetten || style="width: 30%; background-color: #d05454;"| |- |Thürnen || style="width: 30%; background-color: #99FF99;"|Argus |- |Thusis || style="width: 30%; background-color: #d05454;"| |- |Thyon || style="width: 30%; background-color: #d05454;"| |- |Tiefencastel || style="width: 30%; background-color: #d05454;"| |- |Tinizong || style="width: 30%; background-color: #d05454;"| |- |Titterten || style="width: 30%; background-color: #99FF99;"|Argus |- |Tobel || style="width: 30%; background-color: #d05454;"| |- |Toffen || style="width: 30%; background-color: #d05454;"| |- |Tolochenaz || style="width: 30%; background-color: #d05454;"| |- |Toos || style="width: 30%; background-color: #d05454;"| |- |Törbel || style="width: 30%; background-color: #d05454;"| |- |Torgon || style="width: 30%; background-color: #d05454;"| |- |Torny-le-Grand || style="width: 30%; background-color: #d05454;"| |- |Torre || style="width: 30%; background-color: #d05454;"| |- |Torre || style="width: 30%; background-color: #d05454;"| |- |Torricella || style="width: 30%; background-color: #d05454;"| |- |Trachselwald || style="width: 30%; background-color: #d05454;"| |- |Trachslau || style="width: 30%; background-color: #d05454;"| |- |Tramelan || style="width: 30%; background-color: #d05454;"| |- |Trans || style="width: 30%; background-color: #d05454;"| |- |Trasadingen || style="width: 30%; background-color: #d05454;"| |- |Travers || style="width: 30%; background-color: #d05454;"| |- |Treiten || style="width: 30%; background-color: #d05454;"| |- |Trélex || style="width: 30%; background-color: #d05454;"| |- |Tremona || style="width: 30%; background-color: #d05454;"| |- |Trey || style="width: 30%; background-color: #d05454;"| |- |Treycovagnes || style="width: 30%; background-color: #d05454;"| |- |Treyfayes || style="width: 30%; background-color: #d05454;"| |- |Treytorrens (Payerne) || style="width: 30%; background-color: #d05454;"| |- |Treyvaux || style="width: 30%; background-color: #d05454;"| |- |Triboltingen || style="width: 30%; background-color: #d05454;"| |- |Triengen || style="width: 30%; background-color: #d05454;"| |- |Trient || style="width: 30%; background-color: #d05454;"| |- |Trimbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Trimmis || style="width: 30%; background-color: #d05454;"| |- |Trimstein || style="width: 30%; background-color: #d05454;"| |- |Trin || style="width: 30%; background-color: #d05454;"| |- |Trin Mulin || style="width: 30%; background-color: #d05454;"| |- |Trogen || style="width: 30%; background-color: #d05454;"| |- |Trogne (St-Martin) || style="width: 30%; background-color: #d05454;"| |- |Troinex || style="width: 30%; background-color: #d05454;"| |- |Troistorrents || style="width: 30%; background-color: #d05454;"| |- |Trub || style="width: 30%; background-color: #d05454;"| |- |Trübbach || style="width: 30%; background-color: #d05454;"| |- |Trubschachen || style="width: 30%; background-color: #d05454;"| |- |Trüllikon || style="width: 30%; background-color: #d05454;"| |- |Trun || style="width: 30%; background-color: #d05454;"| |- |Truttikon || style="width: 30%; background-color: #d05454;"| |- |Tschappina || style="width: 30%; background-color: #d05454;"| |- |Tscheppach || style="width: 30%; background-color: #d05454;"| |- |Tscherlach || style="width: 30%; background-color: #d05454;"| |- |Tschiertschen || style="width: 30%; background-color: #d05454;"| |- |Tschierv || style="width: 30%; background-color: #d05454;"| |- |Tschingel || style="width: 30%; background-color: #d05454;"| |- |Tschlin || style="width: 30%; background-color: #d05454;"| |- |Tschugg || style="width: 30%; background-color: #d05454;"| |- |Tübach || style="width: 30%; background-color: #d05454;"| |- |Tuggen || style="width: 30%; background-color: #d05454;"| |- |Tumegl/Tomils || style="width: 30%; background-color: #d05454;"| |- |Turbach || style="width: 30%; background-color: #d05454;"| |- |Turbenthal || style="width: 30%; background-color: #d05454;"| |- |Turgi || style="width: 30%; background-color: #99FF99;"|Argus |- |Turin (Salins) || style="width: 30%; background-color: #d05454;"| |- |Turtmann || style="width: 30%; background-color: #d05454;"| |- |Tüscherz-Alfermée || style="width: 30%; background-color: #d05454;"| |- |Tuttwil || style="width: 30%; background-color: #d05454;"| |- |Twann || style="width: 30%; background-color: #d05454;"| |- |Udligenswil || style="width: 30%; background-color: #d05454;"| |- |Ueberstorf || style="width: 30%; background-color: #99FF99;"|Argus |- |Uebeschi || style="width: 30%; background-color: #d05454;"| |- |Ueken || style="width: 30%; background-color: #d05454;"| |- |Uerikon || style="width: 30%; background-color: #d05454;"| |- |Uerkheim || style="width: 30%; background-color: #d05454;"| |- |Uerschhausen || style="width: 30%; background-color: #d05454;"| |- |Uerzlikon || style="width: 30%; background-color: #d05454;"| |- |Uesslingen || style="width: 30%; background-color: #d05454;"| |- |Uetendorf || style="width: 30%; background-color: #d05454;"| |- |Uetikon am See || style="width: 30%; background-color: #d05454;"| |- |Uetliberg || style="width: 30%; background-color: #d05454;"| |- |Uetliburg SG || style="width: 30%; background-color: #d05454;"| |- |Uettligen || style="width: 30%; background-color: #d05454;"| |- |Uezwil || style="width: 30%; background-color: #d05454;"| |- |Uffikon || style="width: 30%; background-color: #d05454;"| |- |Ufhusen || style="width: 30%; background-color: #d05454;"| |- |Uhwiesen || style="width: 30%; background-color: #d05454;"| |- |Uitikon Waldegg || style="width: 30%; background-color: #99FF99;"|Argus |- |Ulisbach || style="width: 30%; background-color: #d05454;"| |- |Ulmiz || style="width: 30%; background-color: #d05454;"| |- |Ulrichen || style="width: 30%; background-color: #d05454;"| |- |Umiken || style="width: 30%; background-color: #99FF99;"|Argus |- |Undervelier || style="width: 30%; background-color: #d05454;"| |- |Unterägeri || style="width: 30%; background-color: #d05454;"| |- |Unterbach BE || style="width: 30%; background-color: #d05454;"| |- |Unterbäch VS || style="width: 30%; background-color: #d05454;"| |- |Untereggen || style="width: 30%; background-color: #d05454;"| |- |Unterems || style="width: 30%; background-color: #d05454;"| |- |Unterendingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Unterengstringen || style="width: 30%; background-color: #d05454;"| |- |Unterentfelden || style="width: 30%; background-color: #99FF99;"|Argus |- |Unterhörstetten || style="width: 30%; background-color: #d05454;"| |- |Unteriberg || style="width: 30%; background-color: #d05454;"| |- |Unterkulm || style="width: 30%; background-color: #d05454;"| |- |Unterlangenegg || style="width: 30%; background-color: #d05454;"| |- |Unterlunkhofen || style="width: 30%; background-color: #d05454;"| |- |Unterramsern || style="width: 30%; background-color: #d05454;"| |- |Unterrindal || style="width: 30%; background-color: #d05454;"| |- |Unterschächen || style="width: 30%; background-color: #d05454;"| |- |Unterseen || style="width: 30%; background-color: #d05454;"| |- |Untersiggenthal || style="width: 30%; background-color: #99FF99;"|Argus |- |Unterstammheim || style="width: 30%; background-color: #d05454;"| |- |Untersteckholz || style="width: 30%; background-color: #d05454;"| |- |Unterterzen || style="width: 30%; background-color: #d05454;"| |- |Untervaz || style="width: 30%; background-color: #d05454;"| |- |Unterwasser || style="width: 30%; background-color: #d05454;"| |- |Uors (Lumnezia) || style="width: 30%; background-color: #d05454;"| |- |Urdorf || style="width: 30%; background-color: #d05454;"| |- |Urmein || style="width: 30%; background-color: #d05454;"| |- |Urnäsch || style="width: 30%; background-color: #d05454;"| |- |Urnerboden || style="width: 30%; background-color: #d05454;"| |- |Ursenbach || style="width: 30%; background-color: #d05454;"| |- |Ursins || style="width: 30%; background-color: #d05454;"| |- |Urswil || style="width: 30%; background-color: #d05454;"| |- |Ursy || style="width: 30%; background-color: #d05454;"| |- |Urtenen-Schönbühl || style="width: 30%; background-color: #d05454;"| |- |Uster || style="width: 30%; background-color: #d05454;"| |- |Uttigen || style="width: 30%; background-color: #d05454;"| |- |Uttwil || style="width: 30%; background-color: #d05454;"| |- |Utzenstorf || style="width: 30%; background-color: #d05454;"| |- |Utzigen || style="width: 30%; background-color: #d05454;"| |- |Uvrier || style="width: 30%; background-color: #d05454;"| |- |Uznach || style="width: 30%; background-color: #d05454;"| |- |Uzwil || style="width: 30%; background-color: #d05454;"| |- |Vacallo || style="width: 30%; background-color: #d05454;"| |- |Vadura || style="width: 30%; background-color: #d05454;"| |- |Vaglio || style="width: 30%; background-color: #d05454;"| |- |Vairano || style="width: 30%; background-color: #d05454;"| |- |Val-d‘Illiez || style="width: 30%; background-color: #d05454;"| |- |Valangin || style="width: 30%; background-color: #d05454;"| |- |Valbella || style="width: 30%; background-color: #d05454;"| |- |Valchava || style="width: 30%; background-color: #d05454;"| |- |Valendas || style="width: 30%; background-color: #d05454;"| |- |Valens || style="width: 30%; background-color: #d05454;"| |- |Valeyres-sous-Montagny || style="width: 30%; background-color: #d05454;"| |- |Valeyres-sous-Rances || style="width: 30%; background-color: #d05454;"| |- |Valeyres-sous-Ursins || style="width: 30%; background-color: #d05454;"| |- |Valeyres-sous-Ursins || style="width: 30%; background-color: #d05454;"| |- |Vallamand || style="width: 30%; background-color: #d05454;"| |- |Vallon || style="width: 30%; background-color: #d05454;"| |- |Vallorbe || style="width: 30%; background-color: #d05454;"| |- |Vals || style="width: 30%; background-color: #d05454;"| |- |Valzeina || style="width: 30%; background-color: #d05454;"| |- |Vandoeuvres || style="width: 30%; background-color: #d05454;"| |- |Varen || style="width: 30%; background-color: #d05454;"| |- |Varenzo || style="width: 30%; background-color: #d05454;"| |- |Vasön || style="width: 30%; background-color: #d05454;"| |- |Vättis || style="width: 30%; background-color: #d05454;"| |- |Vattiz || style="width: 30%; background-color: #d05454;"| |- |Vauderens || style="width: 30%; background-color: #d05454;"| |- |Vauffelin || style="width: 30%; background-color: #d05454;"| |- |Vaugondry || style="width: 30%; background-color: #d05454;"| |- |Vaulion || style="width: 30%; background-color: #d05454;"| |- |Vaulruz || style="width: 30%; background-color: #99FF99;"|Argus |- |Vaumarcus || style="width: 30%; background-color: #d05454;"| |- |Vaux-sur-Morges || style="width: 30%; background-color: #d05454;"| |- |Vaz/Obervaz || style="width: 30%; background-color: #d05454;"| |- |Vella || style="width: 30%; background-color: #d05454;"| |- |Vellerat || style="width: 30%; background-color: #d05454;"| |- |Veltheim AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Vendlincourt || style="width: 30%; background-color: #d05454;"| |- |Vens (Sembrancher) || style="width: 30%; background-color: #d05454;"| |- |Venthône || style="width: 30%; background-color: #d05454;"| |- |Verbier || style="width: 30%; background-color: #d05454;"| |- |Vercorin || style="width: 30%; background-color: #d05454;"| |- |Verdabbio || style="width: 30%; background-color: #d05454;"| |- |Verdasio || style="width: 30%; background-color: #d05454;"| |- |Vergeletto || style="width: 30%; background-color: #d05454;"| |- |Vermes || style="width: 30%; background-color: #d05454;"| |- |Vernamiège || style="width: 30%; background-color: #d05454;"| |- |Vernate || style="width: 30%; background-color: #d05454;"| |- |Vernayaz || style="width: 30%; background-color: #d05454;"| |- |Vernier || style="width: 30%; background-color: #d05454;"| |- |Vérossaz || style="width: 30%; background-color: #d05454;"| |- |Vers-chez-Perrin || style="width: 30%; background-color: #d05454;"| |- |Vers-l‘Eglise || style="width: 30%; background-color: #d05454;"| |- |Versam || style="width: 30%; background-color: #d05454;"| |- |Verscio || style="width: 30%; background-color: #d05454;"| |- |Versegères || style="width: 30%; background-color: #d05454;"| |- |Versoix || style="width: 30%; background-color: #d05454;"| |- |Vésenaz || style="width: 30%; background-color: #d05454;"| |- |Vesin || style="width: 30%; background-color: #d05454;"| |- |Vessy || style="width: 30%; background-color: #d05454;"| |- |Vétroz || style="width: 30%; background-color: #d05454;"| |- |Vevey || style="width: 30%; background-color: #d05454;"| |- |Vex || style="width: 30%; background-color: #d05454;"| |- |Veyras || style="width: 30%; background-color: #d05454;"| |- |Veyrier || style="width: 30%; background-color: #d05454;"| |- |Veysonnaz || style="width: 30%; background-color: #d05454;"| |- |Veytaux || style="width: 30%; background-color: #d05454;"| |- |Vezia || style="width: 30%; background-color: #d05454;"| |- |Vezio || style="width: 30%; background-color: #d05454;"| |- |Viano || style="width: 30%; background-color: #d05454;"| |- |Vich || style="width: 30%; background-color: #d05454;"| |- |Vichères (Liddes) || style="width: 30%; background-color: #d05454;"| |- |Vico Morcote || style="width: 30%; background-color: #d05454;"| |- |Vicosoprano || style="width: 30%; background-color: #d05454;"| |- |Vicques || style="width: 30%; background-color: #d05454;"| |- |Vielbringen b. Worb || style="width: 30%; background-color: #d05454;"| |- |Viganello || style="width: 30%; background-color: #d05454;"| |- |Vignogn || style="width: 30%; background-color: #d05454;"| |- |Vilars NE || style="width: 30%; background-color: #d05454;"| |- |Villa (Ayent) || style="width: 30%; background-color: #d05454;"| |- |Villa Bedretto || style="width: 30%; background-color: #d05454;"| |- |Villa Luganese || style="width: 30%; background-color: #d05454;"| |- |Villaraboud || style="width: 30%; background-color: #d05454;"| |- |Villarbeney || style="width: 30%; background-color: #d05454;"| |- |Villard-sur-Chamby || style="width: 30%; background-color: #d05454;"| |- |Villarepos || style="width: 30%; background-color: #d05454;"| |- |Villargiroud || style="width: 30%; background-color: #99FF99;"|Argus |- |Villariaz || style="width: 30%; background-color: #d05454;"| |- |Villarimboud || style="width: 30%; background-color: #99FF99;"|Argus |- |Villarlod || style="width: 30%; background-color: #99FF99;"|Argus |- |Villars-Bozon || style="width: 30%; background-color: #d05454;"| |- |Villars-Bramard || style="width: 30%; background-color: #d05454;"| |- |Villars-Burquin || style="width: 30%; background-color: #d05454;"| |- |Villars-Epeney || style="width: 30%; background-color: #d05454;"| |- |Villars-le-Comte || style="width: 30%; background-color: #d05454;"| |- |Villars-le-Grand || style="width: 30%; background-color: #d05454;"| |- |Villars-le-Terroir || style="width: 30%; background-color: #d05454;"| |- |Villars-Mendraz || style="width: 30%; background-color: #d05454;"| |- |Villars-sous-Champvent || style="width: 30%; background-color: #d05454;"| |- |Villars-sous-Mont || style="width: 30%; background-color: #d05454;"| |- |Villars-sous-Yens || style="width: 30%; background-color: #d05454;"| |- |Villars-Ste-Croix || style="width: 30%; background-color: #d05454;"| |- |Villars-sur-Font || style="width: 30%; background-color: #d05454;"| |- |Villars-sur-Glâne || style="width: 30%; background-color: #d05454;"| |- |Villars-sur-Ollon || style="width: 30%; background-color: #d05454;"| |- |Villars-Tiercelin || style="width: 30%; background-color: #d05454;"| |- |Villarsel-le-Gibloux || style="width: 30%; background-color: #99FF99;"|Argus |- |Villarsel-sur-Marly || style="width: 30%; background-color: #d05454;"| |- |Villarsiviriaux || style="width: 30%; background-color: #99FF99;"|Argus |- |Villarvolard || style="width: 30%; background-color: #d05454;"| |- |Villarzel || style="width: 30%; background-color: #d05454;"| |- |Villaz-St-Pierre || style="width: 30%; background-color: #d05454;"| |- |Villeneuve FR || style="width: 30%; background-color: #d05454;"| |- |Villeneuve VD || style="width: 30%; background-color: #d05454;"| |- |Villeret || style="width: 30%; background-color: #d05454;"| |- |Villette || style="width: 30%; background-color: #d05454;"| |- |Villette (Lavaux) || style="width: 30%; background-color: #d05454;"| |- |Villiers || style="width: 30%; background-color: #d05454;"| |- |Villigen || style="width: 30%; background-color: #99FF99;"|Argus |- |Villmergen || style="width: 30%; background-color: #d05454;"| |- |Villnachern || style="width: 30%; background-color: #d05454;"| |- |Vilters || style="width: 30%; background-color: #d05454;"| |- |Vinelz || style="width: 30%; background-color: #d05454;"| |- |Vinzel || style="width: 30%; background-color: #d05454;"| |- |Vionnaz || style="width: 30%; background-color: #d05454;"| |- |Vira (Gambarogno) || style="width: 30%; background-color: #d05454;"| |- |Visp || style="width: 30%; background-color: #d05454;"| |- |Visperterminen || style="width: 30%; background-color: #d05454;"| |- |Vissoie || style="width: 30%; background-color: #d05454;"| |- |Vitznau || style="width: 30%; background-color: #d05454;"| |- |Vnà || style="width: 30%; background-color: #d05454;"| |- |Vogorno || style="width: 30%; background-color: #d05454;"| |- |Volken || style="width: 30%; background-color: #d05454;"| |- |Volketswil || style="width: 30%; background-color: #d05454;"| |- |Vollèges || style="width: 30%; background-color: #d05454;"| |- |Vordemwald || style="width: 30%; background-color: #99FF99;"|Argus |- |Vorderthal || style="width: 30%; background-color: #d05454;"| |- |Vouvry || style="width: 30%; background-color: #d05454;"| |- |Vrin || style="width: 30%; background-color: #d05454;"| |- |Vuadens || style="width: 30%; background-color: #d05454;"| |- |Vuarmarens || style="width: 30%; background-color: #d05454;"| |- |Vuarrens || style="width: 30%; background-color: #d05454;"| |- |Vucherens || style="width: 30%; background-color: #d05454;"| |- |Vufflens-la-Ville || style="width: 30%; background-color: #d05454;"| |- |Vufflens-le-Château || style="width: 30%; background-color: #d05454;"| |- |Vugelles-La Mothe || style="width: 30%; background-color: #d05454;"| |- |Vuibroye || style="width: 30%; background-color: #d05454;"| |- |Vuippens || style="width: 30%; background-color: #d05454;"| |- |Vuissens || style="width: 30%; background-color: #d05454;"| |- |Vuisternens-devant-Romont || style="width: 30%; background-color: #d05454;"| |- |Vuisternens-en-Ogoz || style="width: 30%; background-color: #99FF99;"|Argus |- |Vuiteboeuf || style="width: 30%; background-color: #d05454;"| |- |Vulliens || style="width: 30%; background-color: #d05454;"| |- |Vullierens || style="width: 30%; background-color: #d05454;"| |- |Vulpera || style="width: 30%; background-color: #d05454;"| |- |Wabern || style="width: 30%; background-color: #99FF99;"|Argus |- |Wädenswil || style="width: 30%; background-color: #d05454;"| |- |Wagen || style="width: 30%; background-color: #d05454;"| |- |Wagenhausen || style="width: 30%; background-color: #d05454;"| |- |Wagerswil || style="width: 30%; background-color: #d05454;"| |- |Wahlen b. Laufen || style="width: 30%; background-color: #99FF99;"|Argus |- |Wahlendorf || style="width: 30%; background-color: #d05454;"| |- |Walchwil || style="width: 30%; background-color: #d05454;"| |- |Wald AR || style="width: 30%; background-color: #d05454;"| |- |Wald ZH || style="width: 30%; background-color: #d05454;"| |- |Walde AG || style="width: 30%; background-color: #d05454;"| |- |Walde SG || style="width: 30%; background-color: #d05454;"| |- |Waldegg BE || style="width: 30%; background-color: #d05454;"| |- |Waldenburg || style="width: 30%; background-color: #99FF99;"|Argus |- |Waldhäusern AG || style="width: 30%; background-color: #d05454;"| |- |Wäldi || style="width: 30%; background-color: #d05454;"| |- |Waldkirch || style="width: 30%; background-color: #d05454;"| |- |Waldstatt || style="width: 30%; background-color: #d05454;"| |- |Walenstadt || style="width: 30%; background-color: #d05454;"| |- |Walenstadtberg || style="width: 30%; background-color: #d05454;"| |- |Walkringen || style="width: 30%; background-color: #d05454;"| |- |Wallbach || style="width: 30%; background-color: #99FF99;"|Argus |- |Wallenbuch || style="width: 30%; background-color: #d05454;"| |- |Wallenried || style="width: 30%; background-color: #d05454;"| |- |Wallenwil || style="width: 30%; background-color: #d05454;"| |- |Wallisellen || style="width: 30%; background-color: #d05454;"| |- |Walliswil b. Niederbipp || style="width: 30%; background-color: #d05454;"| |- |Walliswil b. Wangen || style="width: 30%; background-color: #d05454;"| |- |Walperswil || style="width: 30%; background-color: #d05454;"| |- |Waltalingen || style="width: 30%; background-color: #d05454;"| |- |Waltensburg/Vuorz || style="width: 30%; background-color: #d05454;"| |- |Waltenschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Walterswil BE || style="width: 30%; background-color: #d05454;"| |- |Walterswil SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Walzenhausen || style="width: 30%; background-color: #d05454;"| |- |Wangen an der Aare || style="width: 30%; background-color: #99FF99;"|Argus |- |Wangen b. Olten || style="width: 30%; background-color: #99FF99;"|Argus |- |Wangen SZ || style="width: 30%; background-color: #d05454;"| |- |Wangen ZH || style="width: 30%; background-color: #d05454;"| |- |Wangenried || style="width: 30%; background-color: #d05454;"| |- |Wängi || style="width: 30%; background-color: #d05454;"| |- |Wangs || style="width: 30%; background-color: #d05454;"| |- |Wanzwil || style="width: 30%; background-color: #d05454;"| |- |Warth || style="width: 30%; background-color: #d05454;"| |- |Wasen im Emmental || style="width: 30%; background-color: #d05454;"| |- |Wassen UR || style="width: 30%; background-color: #d05454;"| |- |Wasterkingen || style="width: 30%; background-color: #d05454;"| |- |Watt || style="width: 30%; background-color: #d05454;"| |- |Wattenwil || style="width: 30%; background-color: #d05454;"| |- |Wattwil || style="width: 30%; background-color: #d05454;"| |- |Wauwil || style="width: 30%; background-color: #d05454;"| |- |Wavre || style="width: 30%; background-color: #d05454;"| |- |Weesen || style="width: 30%; background-color: #d05454;"| |- |Wegenstetten || style="width: 30%; background-color: #99FF99;"|Argus |- |Weggis || style="width: 30%; background-color: #d05454;"| |- |Weiach || style="width: 30%; background-color: #99FF99;"|Argus |- |Weier im Emmental || style="width: 30%; background-color: #d05454;"| |- |Weinfelden || style="width: 30%; background-color: #d05454;"| |- |Weingarten-Kalthäusern || style="width: 30%; background-color: #d05454;"| |- |Weiningen TG || style="width: 30%; background-color: #d05454;"| |- |Weiningen ZH || style="width: 30%; background-color: #d05454;"| |- |Weissbad || style="width: 30%; background-color: #d05454;"| |- |Weissenburg || style="width: 30%; background-color: #d05454;"| |- |Weissenstein b. Solothurn || style="width: 30%; background-color: #d05454;"| |- |Weisslingen || style="width: 30%; background-color: #d05454;"| |- |Weisstannen || style="width: 30%; background-color: #d05454;"| |- |Weite || style="width: 30%; background-color: #d05454;"| |- |Welschenrohr || style="width: 30%; background-color: #99FF99;"|Argus |- |Wengen || style="width: 30%; background-color: #d05454;"| |- |Wengi b. Büren || style="width: 30%; background-color: #d05454;"| |- |Wengi b. Frutigen || style="width: 30%; background-color: #d05454;"| |- |Wenslingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Werdenberg || style="width: 30%; background-color: #d05454;"| |- |Wergenstein || style="width: 30%; background-color: #d05454;"| |- |Wermatswil || style="width: 30%; background-color: #d05454;"| |- |Wernetshausen || style="width: 30%; background-color: #d05454;"| |- |Werthenstein || style="width: 30%; background-color: #d05454;"| |- |Wettingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Wettswil || style="width: 30%; background-color: #d05454;"| |- |Wetzikon TG || style="width: 30%; background-color: #d05454;"| |- |Wetzikon ZH || style="width: 30%; background-color: #d05454;"| |- |Wichtrach || style="width: 30%; background-color: #d05454;"| |- |Widen || style="width: 30%; background-color: #d05454;"| |- |Widnau || style="width: 30%; background-color: #d05454;"| |- |Wiedlisbach || style="width: 30%; background-color: #d05454;"| |- |Wienacht-Tobel || style="width: 30%; background-color: #d05454;"| |- |Wiesen GR || style="width: 30%; background-color: #d05454;"| |- |Wiesenberg || style="width: 30%; background-color: #d05454;"| |- |Wiesendangen || style="width: 30%; background-color: #d05454;"| |- |Wiezikon b. Sirnach || style="width: 30%; background-color: #d05454;"| |- |Wiggen || style="width: 30%; background-color: #d05454;"| |- |Wiggiswil || style="width: 30%; background-color: #d05454;"| |- |Wigoltingen || style="width: 30%; background-color: #d05454;"| |- |Wikon || style="width: 30%; background-color: #d05454;"| |- |Wil AG || style="width: 30%; background-color: #99FF99;"|Argus |- |Wil SG || style="width: 30%; background-color: #d05454;"| |- |Wil ZH || style="width: 30%; background-color: #d05454;"| |- |Wila || style="width: 30%; background-color: #d05454;"| |- |Wilchingen || style="width: 30%; background-color: #d05454;"| |- |Wildberg || style="width: 30%; background-color: #d05454;"| |- |Wildegg || style="width: 30%; background-color: #99FF99;"|Argus |- |Wilderswil || style="width: 30%; background-color: #d05454;"| |- |Wildhaus || style="width: 30%; background-color: #d05454;"| |- |Wilen (Gottshaus) || style="width: 30%; background-color: #d05454;"| |- |Wilen (Sarnen) || style="width: 30%; background-color: #d05454;"| |- |Wilen b. Neunforn || style="width: 30%; background-color: #d05454;"| |- |Wilen b. Wil || style="width: 30%; background-color: #d05454;"| |- |Wilen b. Wollerau || style="width: 30%; background-color: #99FF99;"|Argus |- |Wiler (Lötschen) || style="width: 30%; background-color: #d05454;"| |- |Wiler b. Seedorf || style="width: 30%; background-color: #d05454;"| |- |Wiler b.Utzenstorf || style="width: 30%; background-color: #d05454;"| |- |Wileroltigen || style="width: 30%; background-color: #d05454;"| |- |Wiliberg || style="width: 30%; background-color: #d05454;"| |- |Wilihof || style="width: 30%; background-color: #d05454;"| |- |Willadingen || style="width: 30%; background-color: #d05454;"| |- |Willerzell || style="width: 30%; background-color: #d05454;"| |- |Willisau || style="width: 30%; background-color: #d05454;"| |- |Willisdorf || style="width: 30%; background-color: #d05454;"| |- |Wimmis || style="width: 30%; background-color: #d05454;"| |- |Winden || style="width: 30%; background-color: #d05454;"| |- |Windisch || style="width: 30%; background-color: #99FF99;"|Argus |- |Windlach || style="width: 30%; background-color: #99FF99;"|Argus |- |Winikon || style="width: 30%; background-color: #d05454;"| |- |Winistorf || style="width: 30%; background-color: #d05454;"| |- |Winkel || style="width: 30%; background-color: #d05454;"| |- |Winterberg ZH || style="width: 30%; background-color: #d05454;"| |- |Wintersingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Winterthur || style="width: 30%; background-color: #d05454;"| |- |Winznau || style="width: 30%; background-color: #99FF99;"|Argus |- |Wirzweli || style="width: 30%; background-color: #d05454;"| |- |Wisen SO || style="width: 30%; background-color: #99FF99;"|Argus |- |Wislikofen || style="width: 30%; background-color: #99FF99;"|Argus |- |Wittenbach || style="width: 30%; background-color: #d05454;"| |- |Wittenwil || style="width: 30%; background-color: #d05454;"| |- |Witterswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Wittinsburg || style="width: 30%; background-color: #d05454;"| |- |Wittnau || style="width: 30%; background-color: #99FF99;"|Argus |- |Wittwil || style="width: 30%; background-color: #d05454;"| |- |Wohlen AG || style="width: 30%; background-color: #d05454;"| |- |Wohlen b. Bern || style="width: 30%; background-color: #d05454;"| |- |Wohlenschwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Wolfenschiessen || style="width: 30%; background-color: #d05454;"| |- |Wolfertswil || style="width: 30%; background-color: #d05454;"| |- |Wolfhalden || style="width: 30%; background-color: #d05454;"| |- |Wolfhausen || style="width: 30%; background-color: #d05454;"| |- |Wolfisberg || style="width: 30%; background-color: #d05454;"| |- |Wölflinswil || style="width: 30%; background-color: #99FF99;"|Argus |- |Wolfwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Wolhusen || style="width: 30%; background-color: #d05454;"| |- |Wollerau || style="width: 30%; background-color: #99FF99;"|Argus |- |Worb || style="width: 30%; background-color: #d05454;"| |- |Worben || style="width: 30%; background-color: #d05454;"| |- |Worblaufen || style="width: 30%; background-color: #d05454;"| |- |Wöschnau || style="width: 30%; background-color: #99FF99;"|Argus |- |Wünnewil || style="width: 30%; background-color: #d05454;"| |- |Wuppenau || style="width: 30%; background-color: #d05454;"| |- |Würenlingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Würenlos || style="width: 30%; background-color: #99FF99;"|Argus |- |Wynau || style="width: 30%; background-color: #99FF99;"|Argus |- |Wynigen || style="width: 30%; background-color: #d05454;"| |- |Wyssachen || style="width: 30%; background-color: #d05454;"| |- |Yens || style="width: 30%; background-color: #d05454;"| |- |Yverdon-les-Bains || style="width: 30%; background-color: #d05454;"| |- |Yvonand || style="width: 30%; background-color: #d05454;"| |- |Yvorne || style="width: 30%; background-color: #d05454;"| |- |Zauggenried || style="width: 30%; background-color: #d05454;"| |- |Zäziwil || style="width: 30%; background-color: #d05454;"| |- |Zeglingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Zeihen || style="width: 30%; background-color: #99FF99;"|Argus |- |Zeiningen || style="width: 30%; background-color: #99FF99;"|Argus |- |Zell LU || style="width: 30%; background-color: #d05454;"| |- |Zell ZH || style="width: 30%; background-color: #d05454;"| |- |Zénauva || style="width: 30%; background-color: #d05454;"| |- |Zeneggen || style="width: 30%; background-color: #d05454;"| |- |Zermatt || style="width: 30%; background-color: #d05454;"| |- |Zernez || style="width: 30%; background-color: #d05454;"| |- |Zetzwil || style="width: 30%; background-color: #d05454;"| |- |Zezikon || style="width: 30%; background-color: #d05454;"| |- |Ziefen || style="width: 30%; background-color: #99FF99;"|Argus |- |Ziegelbrücke || style="width: 30%; background-color: #d05454;"| |- |Zielebach || style="width: 30%; background-color: #d05454;"| |- |Zignau || style="width: 30%; background-color: #d05454;"| |- |Zihlbrücke || style="width: 30%; background-color: #d05454;"| |- |Zihlschlacht || style="width: 30%; background-color: #d05454;"| |- |Zillis || style="width: 30%; background-color: #d05454;"| |- |Zimmerwald || style="width: 30%; background-color: #d05454;"| |- |Zinal || style="width: 30%; background-color: #d05454;"| |- |Zizers || style="width: 30%; background-color: #d05454;"| |- |Zofingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Zollbrück || style="width: 30%; background-color: #d05454;"| |- |Zollikerberg || style="width: 30%; background-color: #d05454;"| |- |Zollikofen || style="width: 30%; background-color: #d05454;"| |- |Zollikon || style="width: 30%; background-color: #d05454;"| |- |Zuben || style="width: 30%; background-color: #d05454;"| |- |Züberwangen || style="width: 30%; background-color: #d05454;"| |- |Zuchwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Zuckenriet || style="width: 30%; background-color: #d05454;"| |- |Zufikon || style="width: 30%; background-color: #d05454;"| |- |Zug || style="width: 30%; background-color: #d05454;"| |- |Zugerberg || style="width: 30%; background-color: #d05454;"| |- |Zullwil || style="width: 30%; background-color: #99FF99;"|Argus |- |Zumholz || style="width: 30%; background-color: #d05454;"| |- |Zumikon || style="width: 30%; background-color: #d05454;"| |- |Zunzgen || style="width: 30%; background-color: #99FF99;"|Argus |- |Zuoz || style="width: 30%; background-color: #d05454;"| |- |Zürich || style="width: 30%; background-color: #99FF99;"|Argus |- |Zuzgen || style="width: 30%; background-color: #d05454;"| |- |Zuzwil BE || style="width: 30%; background-color: #d05454;"| |- |Zuzwil SG || style="width: 30%; background-color: #d05454;"| |- |Zweidlen || style="width: 30%; background-color: #d05454;"| |- |Zweilütschinen || style="width: 30%; background-color: #d05454;"| |- |Zweisimmen || style="width: 30%; background-color: #d05454;"| |- |Zwieselberg || style="width: 30%; background-color: #d05454;"| |- |Zwillikon || style="width: 30%; background-color: #d05454;"| |- |Zwingen || style="width: 30%; background-color: #99FF99;"|Argus |- |Zwischenflüh || style="width: 30%; background-color: #d05454;"| |} {| class="wikitable" |- !Fürstentum Liechtenstein |- |Balzers || style="width: 30%; background-color: #d05454;"| |- |Eschen || style="width: 30%; background-color: #d05454;"| |- |Gamprin-Bendern || style="width: 30%; background-color: #d05454;"| |- |Mauren FL || style="width: 30%; background-color: #d05454;"| |- |Nendeln || style="width: 30%; background-color: #d05454;"| |- |Planken || style="width: 30%; background-color: #d05454;"| |- |Ruggell || style="width: 30%; background-color: #d05454;"| |- |Schaan || style="width: 30%; background-color: #d05454;"| |- |Schaanwald || style="width: 30%; background-color: #d05454;"| |- |Schellenberg || style="width: 30%; background-color: #d05454;"| |- |Triesen || style="width: 30%; background-color: #d05454;"| |- |Triesenberg || style="width: 30%; background-color: #d05454;"| |- |Vaduz || style="width: 30%; background-color: #d05454;"| |} [[Strassen_und_Orte_benennen_in_der_Schweiz|Zurück zu Strassen und Orte benennen in der Schweiz]] [[Category:Schweiz]] [[Category:Suisse]] 69fb3d7b00cb03555d53aa85d0f22322b5640935 0 13 10791 10790 2016-06-19T20:35:16Z Wottem 21 42 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für den AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Den Editoren seiner Gegend Hilfestellung leisten. * Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. == Anmeldung Area-Manager == Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Schon recht sattelfest in den Editier-Regeln sein *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:''' *Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. *Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. *Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. *Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. *Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. *Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". *Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. *Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *Caradellino (AT) *popel22 (CH) *svx-biker (CH) *pjw65 (CH) === Richtlinien, die Du genau kennen solltest! === '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. === Online-Formular === Folgendes musst Du tun: *Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. *Klicke auf [[WME Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. *Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. *Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt bald) * Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 53ee94af7572309e6382bdaff01df884a7336ef3 0 14 10830 10829 2016-06-19T20:35:21Z Wottem 21 38 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Vielleicht bist Du auch einmal auf einen Fußweg geleitet worden oder in eine Straße, in der Du nicht fahren darfst und fragst Dich, wie sich das vermeiden lässt? Hier findest Du die Antwort auf solche Fragen. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. =Fußwege= <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ==Beispiele== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] Auch wenn diese Typen im Editor unter "nicht routbar" gelistet sind: Waze wird in bestimmten Fällen diese Straßen für das Routing benutzen. Die Erfahrungen haben gezeigt, dass alles, was durch eine Kreuzung verbunden ist, routbar sein kann. Dies passiert ungeachtet der Abbiegepfeile, oder der Fahrtrichtung der Segmente. <br> '''Folgende Gründe können dabei eine Rolle spielen:'''<br> * Keine alternative Route vorhanden resp. kein anderer Fahrweg möglich * Schlechte oder keine Verbindung zum Routing-Server bei der Berechnung einer Route * Kein GPS-Signal oder Platzierung auf falscher Straße in der App * Eine Straßensperre, die keinen anderen Weg zulässt als den Fußweg * Ein Ziel liegt innerhalb dieser Straße, z.B. wenn auf dem Segment Hausnummern eingetragen sind und diese Hausnummer als Navigationsziel eingegeben wurde. * Eine Kombination aus den oben genannten Gründen Deshalb dürfen alle "nicht befahrbaren" Wege, wie der Fußweg oder die Fußgängerzone '''nicht''' mit dem normalen Straßennetz verbunden werden. ==Ein Tipp== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 8abd3bff3a7ff9a362d0e1dac95a103ca594cf8f 0 15 10839 10838 2016-06-19T20:35:21Z Wottem 21 8 Versionen importiert wikitext text/x-wiki [[Category:Suisse]] == Préambule == Waze est une application mobile de navigation pour véhicules. Waze est basé sur un système communautaire. Toutes les cartes sont créées et mises à jour par des utilisateurs de la communauté. Chacun peut apporter sa pierre à l'édifice ! Dans plusieurs pays, Waze a mis en place une carte de base créé de façon automatique. Cette base est toutefois loin d'être parfaite au niveau de la géométrie. De plus, les cartes de base ne contiennent aucune indication sur les noms des rues, noms de villes, types de routes ainsi que sur les autorisations de tourner. En Suisse, nous n'avons pas eu droit à une carte de base. Cela veut dire que toutes les routes doivent être créées par les utilisateurs (traçage, nommage, etc.). Il y a donc un travail conséquent pour obtenir une carte fiable et complète. C'est pourquoi, nous avons besoin de votre aide pour aider l'ensemble de la communauté. == Devenir éditeur de carte == Avant de faire toutes modifications sur la carte, il est nécessaire de lire la documentation en anglais ainsi que la documentation spécifique à la Suisse. Chaque pays dispose de particularité, c'est pourquoi il est nécessaire de se renseigner sur les règles propres à chaque pays. Il existe deux variantes pour éditer la carte : * Editer des routes que vous avez parcouru * Editer une région que vous connaissez === Editer des routes que vous avez parcouru === Lors de l'utilisation de l'application mobile, chacun de vos trajets est enregistré et visible dans votre tableau de bord (My Dashboard). Waze sait par conséquent chaque route que vous avez empruntée. Dès l'instant où vous avez emprunté une route, Waze vous accorde le droit d'éditer cette route sur l'éditeur de carte (WME, Waze Map Editor). Avec ce système vous êtes autorisé à modifier la géométrie, modifier les autorisations de tourner, nommer des routes, etc. Ce droit n'est toutefois pas acquis à vie, après une certaine période, Waze vous retire les droits d'éditions si vous n'avez pas réemprunté cette route dernièrement. === Editer une région que vous connaissez === Si l'édition de la carte vous plaît, vous avez la possibilité de prendre plus de responsabilité en devenant "Area Manager". En devenant Area Manager, vous n'avez plus besoin d'emprunter une route pour obtenir des droits d'éditions sur celle-ci. Vous pouvez devenir Area Manager de votre quartier, votre ville, votre canton voir plus. Pour devenir Area Manager, il faut en faire la demande en remplissant le questionnaire [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Devenir Area Manager] == Permalink == Le permalink est un lien qui se trouve en bas de l'éditeur de carte qui permet d'obtenir un lien de la zone qui est affiché sur votre écran. Ce lien peut s'avérer utile pour obtenir de l'aide sur les forums de discussions. Des informations plus complètes sont disponible sur le [http://www.waze.com/wiki/index.php/Permalink#Permalink Wiki de Waze] (en anglais) == Les serveurs == Waze fonctionne sur deux serveurs distincts, à savoir : * Serveur Etats-Unis, appelé plus fréquemment ''serveur NA'' * Serveur International (tous les pays sauf les USA), appelé plus fréquemment ''serveur INTL'' Il est par conséquent impératif de ce trouver sur le bon serveur. Les éditions faites sur le mauvais serveur ne sont pas prises en compte ! Pour la Suisse, le bon serveur est composé de l'adresse url : http://world.waze.com == Données des moteurs de recherche == Les images satellites visible dans l'éditeur de carte sont issues d'un partenariat en Waze et Bing Maps. '''Attention, Bing Maps autorise Waze de l'utilisation unique des images satellites. Vous ne devez en aucun cas recopier une partie des données de Bing Maps ! Il en va de même pour Google Maps.''' Le non-respect de cette règle peut contraindre Waze a supprimer toutes les informations d'un pays s'il est prouvé que des utilisateurs ont utilisé des données de Google Maps ou Bing Maps. Ce cas est déjà arrivé au Chili. [[Switzerland|Retour au Wiki Suisse]] f2fac24e80766379948b2da2607fbaaab4a55060 0 16 10874 10873 2016-06-19T20:35:38Z Wottem 21 34 Versionen importiert wikitext text/x-wiki {{France Tabs | Edition}} {{Navigation rapide/Edition}} Waze Map Editor (WME) est le principal outil de cartographie de Waze. Il s’agit d’une application web qui fonctionne sur les principaux navigateurs internet. On accède à WME en utilisant le lien suivant : [https://www.waze.com/fr/editor '''Waze Map Editor'''] {{:Waze Map Editor (WME)/S'authentifier|transcludesection=CONTENT}} == {{@|Présentation de l’interface WME}} == [[File : Disposition de WME.png | 350px | right]] L’interface WME se divise en 3 zones principales: # La [[#La barre d'outils|barre d'outils]] # La [[#Zone à onglets|zone d'onglets]] # La [[#Zone d'affichage de la carte|zone d'affichage de la carte]] {{Clear}} {{:Waze Map Editor (WME)/Barre d'outils|transcludesection=CONTENT}} {{:Waze Map Editor (WME)/Zone d'onglets|transcludesection=CONTENT}} {{:Waze Map Editor (WME)/Zone d'affichage de la carte|transcludesection=CONTENT}} {{:Waze Map Editor (WME)/Se déplacer|transcludesection=CONTENT}} {{:Waze Map Editor (WME)/Raccourcis clavier|transcludesection=CONTENT}} 10ffac98325c18487e0f5fd3bb32028128bd94d3 0 17 10937 10936 2016-06-19T20:35:51Z Wottem 21 62 Versionen importiert wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] 5999ed24ce8cad5e75cdf8451e30c5a131007a6e 0 18 10991 10990 2016-06-19T20:35:58Z Wottem 21 53 Versionen importiert wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Highways== * <span style="color:RoyalBlue;">'''Freeway'''</span> => Autoroute * <span style="color:RoyalBlue;">'''Major Highway'''</span> => Semi-autoroute * <span style="color:RoyalBlue;">'''Minor Highway'''</span> => Routes national et principal * <span style="color:RoyalBlue;">'''Ramps'''</span> => Entrée et sortie d'autoroutes ==Streets== * <span style="color:RoyalBlue;">'''Primary Street'''</span> => Route principale * <span style="color:RoyalBlue;">'''Street'''</span> => Tous les autres rues, rues secondaires, etc. * <span style="color:RoyalBlue;">'''Service Road'''</span> => Route d'accès à des services ( essence, restaurant, magasin, Mc Do, etc). ==Other - drivable== * <span style="color:RoyalBlue;">'''Dirt Roads/4x4 Trails'''</span> => route non goudronée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Parking Lot Road'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non-drivable== * <span style="color:RoyalBlue;">'''Walking Trails'''</span> => Chemin pédestre * <span style="color:RoyalBlue;">'''Pedestrian Boardwalk'''</span> => Zone piétones, bords de lac * <span style="color:RoyalBlue;">'''Stairway'''</span> => Escaliers * <span style="color:RoyalBlue;">'''Railroad'''</span> => Chemin de fer * <span style="color:RoyalBlue;">'''Runway/Taxiway'''</span> => Piste attérissage <br>(C'est pour completer la carte. Il n'est pas conseilé de mettre tous les aéroports. Il suffit der mettre un landmark (Airport)!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneaux qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principal (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principal <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisi "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seul les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisé. =Informations importantes= ==Rue de forêt== Il faut penser, que certaines rues de forêt sont seulement permis aux pietons. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: S'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et prinipales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] cc300af2de986e1bef232514c902b4672217f9ff 0 19 11032 11031 2016-06-19T20:36:05Z Wottem 21 40 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} {{Navigation rapide/Edition}} {{User:Deeploz/Notifications|MsgID=001}} ==Vue d'ensemble== Waze maintient sa propre base de données interne des adresses, ou ce qu'on appelle Numéros de maison. Ces adresses sont utilisées uniquement lorsqu'une adresse spécifique est recherchée dans l'éditeur de cartes Waze ou l'application client Waze. Les numéros de maison sont indépendants de toute autre adresse ou fournisseur de cartographie. Les numéros de maison sont des points sur la carte et peuvent être ajustés à un niveau de détail très poussé pour s'assurer que les Wazers soient dirigés à l'emplacement correct pour cette adresse. Il est donc important de prêter attention à tous les détails concernant les numéros de maison pour assurer un routage correct. ==Choses à se rappeler (avertissements / alertes)== * L'interface numéros de rue ne peut pas être activée quand il y a des modifications non enregistrées. * Les numéros de rue ne sont modifiables qu'au niveau de zoom 100 m/200 ft et inférieur. * Les numéros de rue ne peuvent pas être ajoutés à des segments sans nom. * <s>Les numéros de rue ne peuvent pas contenir autre chose que des chiffres (actuellement).</s> * Le nom d'un segment ne peut pas être retiré s'il y a des numéros de rue qui s'y rattachent. == Les nouvelles routes doivent avoir des numéros de rues == Waze ne fera pas d'importations ou de futures fusions de données externes pour les numéros de rue. Il est donc <u>très important</u> que les <u>nouvelles routes</u> que vous tracez aient des numéros de rue ajoutées pour que Waze guide précisément vers ces adresses. ==Activation de l'interface== Pour modifier, mettre à jour ou supprimer des numéros de maison dans une rue, ''sélectionner'' n'importe quel '''segment''' de la rue que vous voulez modifier. Ensuite ''cliquer'' sur le bouton '''Edit House Numbers''' ou ''presser'' la touche '''H'''. *Note : l'interface ne peut pas être activée quand il y a des modifications non enregistrées. ==Utilisation de l'interface== [[Image:Housenumbers wme bigpicture.jpg|right|thumb|Vue des numéros de rue]] Waze sélectionnera les autres segments connectés au segment sélectionné avec le même nom de rue et de ville. Vous pouvez déplacer la carte le long de cette sélection pour modifier les numéros de maison. La zone surlignée autour de la route est la distance par défaut où les numéros de maison sont autorisés à partir de la rue. Si un numéro de maison doit être situé au-delà de cette distance, vous aurez besoin de '''[[#Forcing|Forcer]]''' l'emplacement du numéro ([[#Forcing|discussed below]]). *Note : si vous Zoomez en arrière [[Map_Editor_Interface_and_Controls#Zoom_Control|zoomed]] au dela de 100m/200ft, vous ne pourrez pas modifier les numéros de maison, et il y aura un message en haut au centre de la fenêtre qui dit : "Zoom in to edit" <br clear="all" /> ===Barre d'outils=== Lorsque l'interface des numéros de rue est activée, une nouvelle barre d'outils apparaît avec l'ensemble des boutons concernant les actions spécifiques pour travailler avec les numéros de rue. [[Image:Housenumbers wme toolbar.jpg|center]] Descriptions des boutons de la barre d'outils : [[Image:Housenumbers wme add button.jpg|left]] Cliquez pour ajouter un numéro de rue<br clear="all" /> [[Image:Housenumbers wme save button.jpg|left]] Cliquez pour enregistrer les modifications<br clear="all" /> [[Image:Housenumbers wme undo button.jpg|left]] Cliquez pour annuler le dernier numéro ou la modification<br clear="all" /> [[Image:Housenumbers wme redo button.jpg|left]] Cliquez pour rétablir le dernier numéro ou la modification<br clear="all" /> [[Image:Housenumbers wme close button.jpg|left]] Cliquez pour quitter l'interface<br clear="all" /> ===Marqueurs=== [[Image:Housenumbers wme number active.gif|right]][[Image:Housenumbers wme number active flip.gif|right]] Les 2 images sur la droite montrent à quoi ressemblent les numéros de rue dans l'éditeur. WME décide lequel utiliser et son orientation en fonction de la densité de numéros afin d'optimiser la lisibilité et la manipulation. *Le "X" rouge est le bouton pour effacer. *Le point bleu à l'opposé est la poignée de déplacement. Le numéro devrait être placé au centre du toit de l'habitation. Pour de larges bâtiments, tels que les box de stockage qui ont une adresse unique, déplacer le repère en face de l'entrée piétonne du bâtiment. Pour les adresses à l'intérieur des centres commerciaux, placer le repère au-dessus de l'emplacement du commerce, comme pour une habitation. ===Modification=== *Pour éditer un numéro, ''cliquer'' dans le numéro et entrer le nouveau numéro. *Pour déplacer un numéro, ''cliquer'' dans le numéro ou sur la poignée de déplacement puis ''cliquer'' et ''déplacer'' en utilisant la poignée de déplacement. *Pour effacer un numéro, ''cliquer'' dans le numéro puis ''cliquer'' sur le '''X''' rouge. ===Ajout=== Pour ajouter un numéro de rue, ''Cliquer'' sur le bouton '''Add''' de la barre d'outils. ''Cliquer'' sur l'emplacement de l'habitation ou du commerce. ''Renseigner'' le '''numéro'''. ===Définir le point d'arrêt=== Le point d'arrêt (parfois désigné comme marqueur de segment) est l'emplacement sur ​​le segment, auquel le numéro de rue est attaché. C'est cette position qui sera utilisée pour la navigation. Il est représenté par un point blanc avec un contour bleu attaché à la rue : [[Image:Housenumbers_wme_adjust_stop_point.jpg|center]] Lorsque vous déplacez un numéro de rue ou en ajoutez un, vous verrez une ligne pointillée blanche menant à un point blanc sur la route que vous avez sélectionnée. Ce point blanc est le point d'arrêt pour la navigation à ce numéro de rue. Il peut être déplacé n'importe où sur le segment nommé pour cette adresse. Il ne peut pas être déplacé vers un autre segment, y compris les allées (en ce moment). Le point d'arrêt doit être placé près de l'entrée principale du bâtiment, une entrée ou une entrée du parking du bâtiment. Pensez de cette façon : «Si vous pouvez amener le conducteur à cet endroit et que l'application affiche un point repère directionnel qui annonce le bon côté de la route, le conducteur doit être en mesure de déterminer de quel bâtiment il s'agit" Note : si vous n'avez pas affiché les images satellites, ce qui fait que votre fond de carte est blanc, vous ne serez pas capable de voir la ligne pointillée. Parce que c'est blanc... *L'équipe de développeurs de Waze travaille sur un moyen de spécifier un point d'arrêt sur la rue différent du segment auquel l'adresse est attachée. C'est important pour les emplacements des centres commerciaux, les longs chemins privés non nommés avec des adresses multiples ou des entreprises qui possèdent des entrées de parking en dehors de la rue nommée. A ce jour, il n'y a pas de moyen de guider les conducteurs vers l'intérieur du parking. ==Forçage== <span style="color:#f00;">'''NOTE''': Forcer un numéro de rue est actuellement limité aux éditeurs niveau 3 et plus. Waze cherche à ajuster cela, notamment dans les pays où les numéros de rue n'ont pas toujours la même logique de positionnement.</span> Il y a 2 raisons pour forcer un numéro de rue : #Le numéro de rue n'est pas aligné aux schémas de numérotation habituels pour l'endroit ou le pays #Le numéro de rue est situé plus loin que la distance acceptable de la rue. Les numéros peuvent être localisés au-delà de la distance autorisée ou, en dehors de la séquence, mais lors de la sauvegarde, il vous sera proposé de confirmer le forçage du ou des numéros de rue à cet endroit. [[Image:Housenumbers wme force dialog.jpg|center]] Si vous en avez plusieurs qui nécessite un forçage, une seule confirmation les forcera tous. Donc soyez certains que tous sont correctement positionnés. [[Image:Housenumbers wme_number forced.gif|right]] Lorsqu'un numéro de rue a été forcé et sauvegardé, il sera représenté différemment des autres, avec le mot "Forced" inclus dans le marqueur comme indiqué dans l'image de droite. ==N'oubliez pas de sauvegarder== Avant d'''appuyer'' sur '''Echap''' sur votre clavier ou de ''cliquer'' '''Close''', rappelez-vous de ''cliquer'' sur '''Save'''. 1d969ccc32e632b2139d44afb261736a90157820 0 20 11172 11171 2016-06-19T20:37:21Z Wottem 21 139 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} {{Navigation rapide/Edition}} {{User:Deeploz/Notifications|MsgID=001}} {{User:Deeploz/Notifications|MsgID=003}} <!--Editorial Reminders--> <!--To Do - Bow Tie intersections --> <!--To Do - U-Turn Solutions for "Road not connected" error --> (article en cours de traduction ; les liens suivis de (µ) mènent à des textes en VO et les mots suivis de (∂) mériteraient une définition ou un lien vers une définition) Cet article est un guide pour éditer correctement les carrefours et intersections. Lisez-le et relisez le avant d'éditer la carte ==Plus c'est Simple mieux c'est== Pour représenter une intersection de routes, il ne faut pas vouloir calquer la réalité. Toujours représenter au plus simple et ne complexifier que pour résoudre un problème. == Les Bases &larr; A LIRE EN PREMIER== === Une Intersection dans Waze=== Une Intersection est composée de 3 éléments : # au moins deux segments de route # un ou plusieurs point(s) de jonction (junction node) (∂) # des autorisations ou restrictions de tourner sur ces points de jonction Pour savoir comment créer et modifier routes, jonctions et autorisations de tourner, merci de lire [[Map_Editing_Quick-start_Guide|the Map Editing Quick-start Guide]]. (µ) === Carrefour en T === Commençons par le cas de base, une route rejoint la route principale à un angle de 90°. Les vues physiques et logiques des routes correspondent. : [[Image:Jct_3_90_ex.png]] [[Image:Jct_3_90.png]] Mais les croisements ne se font pas toujours à angle droit. Le premier réflexe sera de représenter la jonction comme elle est dans le monde physique - deux lignes se rejoignant à angle aigu. : [[Image:Jct_3_45_ex1.png]] [[Image:Jct_3_45.png]] Mais cette méthode amène un problème, selon l'angle le client pourra annoncer l'instruction "Restez à droite" quand un "Tournez à droite" serait plus approprié. Si une "Minor Highway" (ou plus) est impliquée, vous obtiendrez un "Sortez à droite" qui peut être source de confusion dans de nombreuses situations. Dans certains cas, aucune instruction ne sera donnée. Dans le pire des cas, le moteur de routage peut déterminer qu'il n'est pas possible de tourner à cause de l'angle trop aigu et proposer un autre trajet. (Dans l'exemple, aller au sud, puis tourner à gauche vers l'est.) Enfin, des "erreurs de carte" (Map Problems) peuvent être générées, le trajet gps des wazers étant "trop ​​loin" du point de jonction réel (par exemple, en voyageant vers le sud, puis à gauche vers l'est). Pour éliminer toute ambiguïté, il faut cartographier la jonction d'un point de vue logique. Pour avoir les instructions "Tournez à gauche" ou "Tournez à droite", il faut la modifier de sorte qu'elle ressemble à un croisement à 90°, pour cela ajouter des nœuds de géométrie (∂) afin que l'embranchement quitte la route principale à 90° (ou presque), puis courber le segment pour rejoindre son vrai tracé. : [[Image:Jct_3_45_curve.png|200px]] Nous avons maintenant une intersection qui fonctionne logiquement comme un carrefour à 90° et correspond aussi à la réalité. Voici un exemple du monde réel qui fournit les instructions de guidage attendues et «attrape» tous les changements de directions sans générer de "map error"(∂) : "roads are too far apart" (les routes sont trop éloignées). : [[Image:Jct_3_45_ex.png|200px]] Pour les bretelles de sortie un ajout de nœud de géométrie (∂) peut aussi être utile quand elles divergent à un angle très faible. : [[Image:Jct_ramp_no_geo_ex.png]] [[Image:Jct_ramp_no_geo.png]] Ici, comme pour l'exemple précédent : dans l'éditeur, il peut être difficile de voir et de cliquer les flèches de restriction de tourner (∂). : [[Image:Jct_ramp_no_geo_arrow.png]] Mais si nous ajoutons des nœuds de géométrie(∂) pour augmenter l'angle de départ à 20°/ 30°. (Plus d'info sur ces angles dans la section [[#Géométrie|Géométrie]] plus bas)... : [[Image:Jct_ramp_w_geo_ex.png]] [[Image:Jct_ramp_w_geo.png]] ...maintenant les flèches sont visibles et accessibles. Notez que vous pouvez également appuyer sur le 's' de votre clavier pour "s"éparer les flèches dans l'éditeur, si vous avez des difficultés pour cliquer les flèches. : [[Image:Jct_ramp_w_geo_arrow.png]] === Carrefour en + === Pour les carrefours à 4 routes on peut avoir la même approche que précédemment. <br> Avec des angles proches de 90 °. : [[Image:Jct_4_90_ex.png]] [[Image:Jct_4_90.png‎ ]] ... ou pas : [[Image:Jct_4_45_ex1.png]] [[Image:Jct_4_45.png]] Zoomer pour ajouter un unique nœud de géométrie (∂) de chaque côté, il sera pratiquement invisible pour les utilisateurs. : [[Image:Jct_4_45_curve.png]] une fois dézoomé cela sera proche de : : [[Image:Jct_4_45_ex.png]] avec ces ajustements on peut prévoir l'annonce faite par le guidage tout en gardant l'aspect réel des routes. == Contrôler les instructions de guidage == Avant de poursuivre, assurez-vous que vous comprenez bien les mécanismes de [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|turn restrictions]] (µ) dans l'éditeur de carte. Si les virages ne sont pas correctement autorisés ou interdits, vous n'obtiendrez jamais les instructions de navigation correctes. Dans la section sur les [[#les_Bases_.E2.86.90_A_LIRE_EN_PREMIER|"bases"]] présentée plus haut, nous avons abordé la façon de s'assurer qu'une instruction "virage à gauche / droite" serait donnée plutôt qu'une instruction "Restez à gauche / droite" moins appropriée. Les détails de la mécanique derrière cela peuvent être trouvés sur la page [[Comment_Waze_détermine_les_instructions_de_guidage_%3F|Comment Waze détermine les instructions de guidage ?]], mais un résumé est présenté dans les sections ci-dessous. === Géométrie === {{ObsoleteSection| Si les jonctions que vous modifiez suivent les principes, il sera beaucoup plus facile de prévoir le guidage d'une jonction sans entrer dans les détails des algorithmes. * Environ '''90°''' d'angle au départ => '''Tourner à droite / tourner à gauche''' * Entre '''20° et 30°''' d'angle au départ si parmi les routes impliquées il y a: ** seulement des "Primary Street" ou inférieur => '''restez à droite / restez à gauche''' ** des "Ramps" (bretelles) et/ou des "Minor Highway" et niveau supérieur => <br> '''Sortez à droite / restez à gauche''' pour les pays où l'on roule à droite, <br> '''restez à Droite / Sortez à Gauche''' pour les pays où l'on roule à gauche * Approximativement '''0''' degré d'angle de départ =>'''pas d'instruction de navigation''' '''NOTE:''' Il y a des exceptions à ces règles car la géométrie n'est pas le seul facteur qui détermine les instructions de guidage. Voir la section [[#Type_et_nom_des_segments|Type et nom des segments]] pour savoir quel impact ils peuvent avoir. Les angles permettent de définir le résultat souhaité (tournez / restez) et ne pas laisser le choix (incertain) à l'algorithme de routage. - 45° est un point de basculement ; bien qu'il semble identique à l'œil, un angle de 44,5° se comporte différemment d'un angle de 45,5°. - sur une [[# Patte-d'oie | patte-d'oie]] pour définir le segment «tout droit» et celui «tourner», avoir un segment à 0° et l'autre à 5° n'est pas clair ni évident. "Tout droit" est plus évident si les angles sont de 0°et 20°. Cette connaissance nous permet de contrôler le guidage à une jonction en modifiant un seul nœud de géométrie dans la plupart des cas. Souvent utile pour les [[At-grade connectors|Carrefours à niveau]] (µ) où, parfois il faut un "restez à droite / gauche" et d'autres fois un «Tourner à droite / gauche» est plus approprié. En venant du Sud pour s'engager sur le "connecteur" qui mène à la route vers l'Est - Garder l'angle de départ dans la plage de 20 à 30 degrés, donnera un "restez à droite" : [[Image:Jct_at_grade_keep.png]] - Mais augmenter l'angle à 90° produira un "tourner à droite" : [[Image:Jct_at_grade_turn.png]] Les mêmes règles s'appliquent à l'autre bout du segment. Un angle de 20° à 30° comme ci-dessus, ne donnera aucune instruction, comme pour une voie d'insertion. En augmentant l'angle à 90°, il y aura un "Tourner à droite". En outre, si la route sud-nord de ce dernier exemple était une Minor/Major Highway , l'angle de 20° à 30° produirait l'instruction "Sortez à droite" qui peut être déroutante par rapport à un "restez à droite" ". Donc, sauf si il s'agit d'une sortie réelle, un angle de 90° est requis pour produire un "Tourner à droite" . }} === Type et nom des segments === Le nom et le type des segments, en plus de la géométrie, influent l'algorithme de routage. {{ObsoleteSection| Si vous voulez une annonce, une différence de nom entre les segments améliorera les chances (pas de garantie). Dans le cas ci-dessus, le "connecteur" doit soit avoir un nom différent de celui de la route" ou pas de nom du tout. (Voir [[At-grade connectors#Road name|Comment nommer les connecteurs]]. (µ) Le type de route est un facteur pour définir les instructions de navigation, mais les noms et les angles sont beaucoup plus importants. Si plusieurs routes débouchent sur un carrefour et deux de ces routes sont alignés à +/- 0° et ont le même nom, ça sera un "tout droit" quelque soient les types de route . Un exemple illustré dans la section : [[#Patte-d'oie | Patte-d'oie]] plus bas. Le type de routes sera LE facteur déterminant lorsque tous les noms sont différents. Par exemple, un segment Ramp1 menant à un segment Freeway et un autre segment Ramp2: *même si Ramp1 et Freeway sont alignés à +/-0° et que Ramp2 part à 20°/ 30° de Ramp1 *Ramp2 sera considérée comme "tout droit" *il n'y aura pas d'annonce pour le chemin Ramp=>Ramp *il y en aura une pour le chemin Ramp=>Freeway, }} == Entre voies == === Patte-d'oie === {{ObsoleteSection| Lorsque les rues se croisent en Y, bien examiner la façon dont elles sont mise en correspondance pour fournir des instructions de navigation utiles. Dans l'exemple ci-dessous, la rue principale se nomme Main St à l'ouest et Atlantic Ave. à l'est. Le changement de nom se produit quand Main St se rétrécie. : [[Image:Jct_Y_ex_aerial.png|200px]] La description ci-dessus est simple, mais d'après l'image ci-dessus, une description plus technique serait que Main St est une ligne droite et Atlantique Av un embranchement. Cartographier de cette façon dans l'éditeur, créerais un gros problème. : [[Image:Jct_Y_ex_map_bad.png|200px]] Comme la partie multi-voies et la partie rétrécie de Main St portent le même nom, le moteur de routage les prend en compte comme "Tout droit" . Les aligner sur la carte telles qu'elles apparaissent vu du ciel, va renforcer cette idée. Pour un conducteur "Tout droit" c'est continuer sur la rue principale, quel que soit sont nom. Afin que le moteur de routage face un traitement approprié de la jonction, il faut "prendre des libertés" avec la géométrie des trois segments concernés et arriver à ça: : [[File:Jct Y ex map.png|200px]] Maintenant "Tout droit" suit la multi-voies de Main St sur Atlantic Ave., puisque la transition aussi proche de 0° que possible. La portion rétrécie de Main St bifurque maintenant à un angle proche de 90°. Le moteur de routage doit reconnaître qu'un "Tourner" est nécessaire. À cette intersection sur le trajet Main St => Atlantic Ave. pas d'annonce, et celui Main St =>Main St annonce un "Tourner à droite. Exactement ce que la plupart des conducteurs attendent. }} === Voies sans issue === ====Impasse, Voie sans issue, Cul-de-sac ==== Une impasse, aussi appelée cul-de-sac ou voie sans issue, est un type de voie ne possédant qu'un seul point d'entrée pour les véhicules, et qui nécessite par conséquent de faire un demi-tour ou une marche arrière pour pouvoir en sortir. {{ObsoleteSection| Vérifier qu'il ya un nœud de jonction (pas juste un nœud de géométrie) à la fin du segment. Cela est nécessaire pour assurer le bon acheminement hors du segment. Sinon corrigez-le en suivant les étapes du [[Creating_and_Editing_street_segments#Fix_the_end-node_on_cul-de-sacs_and_dead-ends|Traitement des impasses.]](µ) : [[Image:Jct_dead_end.png|200px]] Ce noeud de jonction final doit être situé près de la fin de la route, mais rester sur la chaussée pour ne pas nuire aux itinéraires. Waze estime la route parcourue complètement si le conducteur passe sur les jonctions aux deux extrémités . Placer le nœud de jonction final à la même distance de l'extrémité de la chaussée, que de chacun de ses bords. : [[Image:Jct_dead_end_ex.png|200px]] Le Cul-de-sac est une configuration particulière du coté fermée d'une impasse en ampoule Dans presque tous les cas, un cul-de-sac doit être traitée exactement comme les autres impasse, avec le noeud de jonction finale au centre de l'ampoule : [[Image:Jct_cul-de-sac_ex.png|200px]] dans le cas d'un îlot (NE PAS CREER DE ROND-POINT) : [[Image:Jct_cul-de-sac_island_ex.png|200px]] : [[Image:Jct_cul-de-sac_island_ex_road.png|200px]] mais placer le nœud de jonction finale à l'extérieur du périmètre de l'îlot central en sorte que le conducteur puisse passer dessus Toutefois, si l'ampoule du cul-de-sac est grande ainsi que l'îlot, elle peut être traitée comme une [[# Boucle | Boucle]]. 'Une règle de base est que si vous étiez debout à la fin du cul-de-sac, pouvez-vous dire que c'est juste un cul-de-sac? Ou doit-il ressembler à deux chemins différents? Si vous voyez une île, mais ne savez pas si elle est significative, supprimer la boucle sur. Si des "Map Error" "Missing Road" apparaissent, ajouter une boucle.'' }} ==== Boucle ==== Les boucles sont des routes qui ramènent au point de départ sans faire demi-tour. UNE BOUCLE DOIT ÊTRE COMPOSÉE DE TROIS SEGMENTS DE ROUTE DONC, DEUX SEGMENTS DE ROUTE NE DOIVENT PAS AVOIR DEUX JONCTIONS EN COMMUN. Si cette règle n'est pas respectée, le serveur de routage aura du mal à fournir des itinéraires dans et hors de la boucle. Une boucle divisée en trois segments par une jonction n'aura pas ce problème. Si il n'y a pas de segment de route à ajouter pour casser la boucle en trois morceaux, il faut [[Map_Editing_Quick-start_Guide#Splitting_a_segment| insérer un nœud de jonction supplémentaire]](µ) . L'emplacement précis n'a pas d'importance. : [[Image:Jct_loop_bulb_3seg.png]] [[Image:Jct_loop_square_3seg.png ]] '''NOTE:''' Il est facile pour un éditeur de supprimer un noeud de jonction supplémentaire, en supposant qu'il est vraiment superflu, surtout si la boucle est très grande ou sa forme trompeuse. Pour l'éviter ajouter à la carte un chemin ou une allée . '''NOTE:''' L'éditeur de cartes peut renâcler au traitement d'une boucle en refusant d'enregistrer une modification. essayez l'une des approches suivantes: Si la boucle et la route qui y mène portent le même nom: * Sélectionner la boucle et la route * Cliquer sur l'icône pont qui apparaît (une extrémité de la boucle se déconnecte de l'autre) * Diviser la boucle * Reconnecter l'ex-boucle * Vérifier les autorisations de tourner Si la boucle et la route qui y conduit ont des noms différents: * Dessiner un nouveau segment de route qui se connecte à la jonction boucle / route * Donner à ce nouveau segment les même nom et ville que la boucle * Sélectionner la boucle et le nouveau segment de route * Cliquer sur l'icône pont qui apparaît (une extrémité de la boucle se déconnecte de l'autre) * Diviser la boucle * Reconnecter l'ex-boucle * Vérifier les autorisations de tourner [http://www.youtube.com/watch?v=a7yAzG7HElw ici une video YouTube de la 2nd méthode]. === Rond-Point et Giratoire=== : [[Image:Jct_roundabout.png]] Voir la section[[Tout_sur_les_Ronds-Points| tout sur les ronds-points]] ===Connecteurs de carrefour à niveau=== {{ObsoleteSection| : [[Image:Jct_at_grade_keep.png]] A ne pas confondre avec les bretelles! Attention aux autorisations de tourner. Voir la page [[At-grade connectors|Connecteurs de carrefour à niveau]] (µ). }} === Intersections en «noeud papillon» === (mise à jour juillet 2013)<br> La forme «noeud papillon» simplifie une intersection quand une route à double voie (en rouge) et une route à chaussée unique (en marron) se croisent. : [[File:Jct_bowtie.png]] En réduisant l'intersection à un seul point, on améliore le contrôle sur les demi-tours et on évite les segments courts qui peuvent introduire complexité et problèmes de routage. Le premier réflexe serait de cartographier l'intersection comme la route est physiquement construite - en utilisant une forme "H" (un H allongé dans l'illustration) où chaque chaussée rouge à sens unique croise la rue marron. Si cette méthode est utilisée, il n'est pas possible de limiter les demi-tour d'une voie à sens unique à l'autre via la barre centrale du "H" laquelle porte à la fois le trafic «1/2 tour» et «tourne à gauche» venant de la rouge et «tourne à gauche» de la marron. Cartographiée en «noeud papillon», il ya une flèche de guidage spécifique qui peut autoriser ou interdire le demi-tour si nécessaire. La barre centrale du H peut 'compliquer' la carte. Si la marron change de nom à la jonction, le segment central ne doit pas se voir attribué de nom de rue. Le segment héritera du nom approprié en fonction du sens de trajet. Ce segment central est alors différent de ceux de chaque côté, ultérieurement un «Sélectionnez toute la rue» dans l'éditeur ignorera ce segment ce qui peut compliquer l'édition. Enfin, le systèmes de Waze a des difficultés à capter des vitesses moyennes pour les segments courts (moins de 50m ndt) , en particulier lorsque le trafic ne passe pas à travers les segments ce qui peux se produire dans les grands carrefours. Dans l'exemple ci-dessus la barre centrale du H serait totalement verticale, mais le trafic tournant à gauche prendrai un angle à 45°, ajouter l'imprécision de nombreuses puces GPS et des segments seront considérés comme jamais traversés sur certain trajets. Notes : - attention à la géométrie utilisée dans le nœud papillon. Si les angles sont trop important (45° ou plus) un conducteur qui roule le long de l'un segment rouge peut recevoir une instruction «tournez» ou «serrez» à l'intersection au lieu de n'en recevoir aucune. - si la barre centrale du H est longue et/ou permet au trafic de s'arrêter et/ou former une file d'attente, la forme «noeud papillon» peut ne pas être appropriée. Le segment peut être assez long pour justifier d'être cartographié surtout si les routes à sens unique doivent beaucoup s'écarter de leur emplacement physique pour se réunir en un seul point. == Bretelles == Les bretelles ont un rôle spécifique elles servent à connecter les segments de '''Freeway, Major et Minor Highways''' aux autres routes dans les carrefours/échangeurs à dénivelé. === Quand utiliser une Bretelle === {{ObsoleteSection| Les 2 conditions suivantes doivent être remplies # Deux routes se croisent l'une au-dessus de l'autre # Au moins une des routes est ## Minor Highway ## Major Highway ## Freeway ## Bretelle Si ce n'est pas le cas utiliser des 'Connecteurs' (∂) [[#At-Grade_Connectors|At-Grade Connector]].(µ) }} === Comment dessiner une Bretelle === Règle première : '''Plus c'est simple, mieux c'est'''. Souvent un unique segment est nécessaire. L'existence d''''un îlot''' peint, en béton, ou d'herbe '''N'EST PAS''' une raison suffisante pour séparer une bretelle en Y. : [[Image:Jct_ramp_no_split.png]] Lorsque les chemins s'écartent de manière significative à la fin de la bretelle, indépendamment de l'existence de tout type d'îlot, plusieurs bretelles doivent être utilisées. : [[Image:Jct_ramp_split.png]] == Intersections Highway/Freeway == Ce sont les jonctions entre les routes de types Highway/Freeway, ainsi que leurs bretelles. Des exemples spécifiques de la façon de gérer les types de jonction communs sont fournis dans les sections suivantes. ==== Sorties des Highway et Freeway ==== Il s'agit d'une situation de base quand un "tout droit" est évident pour le conducteur et qu'une instruction de navigation n'est requise que pour la sortie. Si les instructions de navigation sont nécessaires pour les deux directions, voir la section [[#Segments de guidage|Segments de guidage]] plus loin. ===== Structure ===== : [[Image:Jct_fwy_exit.png]] [[Image:Jct_maj_exit.png]] [[Image:Jct_min_exit.png]] Pour une sortie basique il faut que: # le segment d'entrée et un segment de sortie soient de type Highway/Freeway. # les segments Highway/Freeway entrée et sortie forment un angle segment 0°) # l'autre segment de sortie est de type bretelle # le segment bretelle de sortie ait un angle 20° à 30° du segment d'entrée Si ces conditions sont remplies pour faire emprunter la bretelle il y aura l'annonce "Sortez à droite" et rien pour continuer tout droit ===== Noms ===== Les segments Highway/Freeway avant et après la jonction doivent porter le même nom (street name). Le segment Bretelle doit être nommé comme précisé dans la section [[Nommage France#Nommage des entrées, sorties et des embranchements d'autoroutes et voies rapides|dénomination des sorties en France]] ===== Exemple ===== : [[Image:Edition-sortie.png]] ==== Scission Highway/Freeway ==== Une scission Highway/Freeway (Split) quand un segment Highway/Freeway forme une intersection avec 2 autres segments Highway/Freeway et que pour le conducteur il n'y a pas de "Tout Droit" évident ===== Structure ===== : [[Image:Jct_fwy_fwy_split.png]] Pour qu'il y ait une instruction de navigation pour chaque branche, les conditions suivantes doivent être remplies: # tout les segments sont de type Highway/Freeway # tout les segments doivent avoir des noms (street name) différents # les segments de sortie forment un angle de départ de 20° à 30° par rapport au segment d'entrée. Si ces conditions sont réunies, chaque branche aura l'instruction "Restez à droite" / "Restez à gauche". ===== Noms ===== La règle principale est que ''les 3 segments à la jonction doivent avoir des noms différents.'' # Utiliser les noms de rue (facile si les trois ont des noms différents). par exemple : '''A1''' se divise en '''A2''' et '''A3''' # Utiliser un nom de direction pour les branches de sortie. par exemple : '''A1''' se divise en '''A1: Lyon''' et '''A3: Bordeaux''' ==== Segments de guidage ==== Il peut être nécessaire de fournir des informations supplémentaires sur une intersection complexe * '''Voies dédiées''' - Highway 3 voies qui continue sur 2 et une voies se sépare. * '''Signalisation absente''' - absence de panneau ou incohérence * '''Sortie à gauche''' - sortie à gauche et le reste du trafic continu à droite Dans ces cas, nous avons besoin d'utiliser de courts segments de guidage qui sont nommés avec l'information affichée sur les panneaux routiers. Il existe deux méthodes pour y parvenir : * '''Highway/Freeways''' ** Pour: ligne continue sur la carte de l'application client ** Pour: pas de "pénalité" pour changement de type de route (même si nous ne savons quel d'impact cela a en réalité) ** Contre: le nom (long) du petit segment peut encombrer la carte ** Contre: segment parfois difficile à voir dans l'éditeur il se confond avec les autres ** Note: génère les instructions de guidage "Restez/Serrez à droite/gauche" * '''Ramps''' ** Pour: Pas de nom long qui encombrent la carte ** Pour: force l'application client à zoomer sur la scission ** Contre: "pénalité" pour changement de type de route (même si nous ne savons quel d'impact cela a en réalité) ** Contre: ligne discontinue sur la carte de l'application client ** Note: génère les instructions de guidage "Serrez/Restez à gauche" et "Sortez à droite" Dans les deux cas, les segments sortants doivent être de même type et avoir des noms différents du segment entrant. *Illustration de la scission de l'Highway X en X et Y ** D'abord la version Freeway:<br/>[[Image:Jct_fwy_fwy_wayfinder_fwy.png]] ** Puis la version Ramp (même nom pour les segments):<br/>[[Image:Jct_fwy_fwy_wayfinder_rmp.png]] * Sur une sortie afin de fournir au conducteur un préavis pour qu'il se place sur la bonne voie de la chaussée pour continuez tout droit ou sortir. ** D'abord la version Freeway:<br/>[[Image:Jct_fwy_rmp_wayfinder_fwy.png]] ** Puis la version Ramp (même nom pour les segments):<br/>[[Image:Jct_fwy_rmp_wayfinder_rmp.png]] Les segments de guidage doivent faire 15 à 20 mètres de long. Le segment reste petit, donc peu visible dans le client, mais assez long pour l'être dans l'éditeur de carte. ==== Scission de Bretelle ==== Une bretelle peut se diviser en deux directions. Si c'est le cas, "Sortez à droite" et "Serrez à gauche" sera annoncé (en utilisant le nom du segment dans le TTS). ===== Structure ===== : [[Image:Jct_ramp_ramp_split.png]] ===== Noms ===== Si une bretelle n'a pas de nom, le nom d'une bretelle finale va se propager vers l'arrière. Dans l'exemple ci-dessus, si les deux bretelles sortant de la jonction sont nommées, la bretelle initiale de la jonction peut être laissée sans nom. L'instruction de navigation dirigeant le conducteur sur la première bretelle utilisera le nom de la bretelle finale appropriée. == Échangeurs == Voir [[Limited_Access_Interchange_Style_Guide|Limited Access Interchange Style Guide]]. == Cas particuliers == === Transitions === Une transition est une absence d'intersection représentée par un nœud de Jonction. : [[Image:Jct_transition.png]] [[Image:Jct_transition_90.png]] Ils servent à # un changement de nom de la route (une départementale à la limite de deux départements) # un changement de sens de circulation (double sens => sens unique) # rendre navigable une [[#Boucle|boucle]] Il y a des nœuds de jonction superflus sur la carte pour diverses raisons: reste d'une jonction avec un segment supprimé, hérité de l'importation du fond de carte (Base Map), pont, tunnel etc... '''Ces nœuds superflus sont à supprimer.''' [[Map_Editing_Quick-start_Guide#Delete_a_Junction|(Guide de suppression d'un nœud)]].(µ) Cela simplifiera la carte, éliminera des restrictions de tourner à définir ou vérifier, et réduira les besoins en ressources informatiques. Supprimer aussi le nœud de géométrie, qui remplacera le nœud de jonction, s'il n'est pas nécessaire. (clic+D sur le nœud) === Route vers nulle part === Dans certain cas, il peut être nécessaire d'ajouter des segments de route qui mènent vers nulle part afin de fournir des instructions de navigation précises. Par exemple pour l'extrémité d'une Freeway en construction. Si la carte est dessinée avec la Freeway se terminant par un segment Bretelle, il n'y aura pas d'annonce pour la dernière sortie. Cela peut être déroutant, imaginez parcourir une autoroute et avoir comme instruction suivante "Tournez à gauche sur rue Alphonse Karr". En ajoutant un segment de la trajectoire future de l'autoroute, le moteur de routage aura une jonction qui va générer une instruction "Sortez" à la fin de l'autoroute, ce qui évite toute confusion. Inversement, si l'instruction "Sortez ... " à la fin de l'autoroute n'est pas utile, il faut s'assurer qu'il n'y a pas de tronçons au-delà de la sortie finale. ===Routes decalées === Quand deux routes se croisent, il arrive que 2 tronçons ne soient pas alignés. : [[Image:Jct_4_offset.png]] Il faut considérer quelques points: # Les routes sont-elles alignées dans la réalité? Si c'est le cas, modifier la jonction en croisement à 4 segments. # Les routes sont-elles PRESQUE alignées dans la réalité ? Si on s'attend à une instruction 'tout droit" plutôt que "Tourner à droite puis Tourner à gauche" modifier la jonction en croisement à 4 segments. Il peut être nécessaire de ne pas coller au plus prés de la ligne médiane de la route. Dans l'exemple suivant les angles sont exagérés pour montrer comment la jonction est forcée pour être proche de 90°, cela peut être beaucoup plus progressif et / ou fait en zoomant.<br/><br/>[[Image:Jct_4_offset_align.png]] [[Image:Jct_4_offset_align_ex.png]]<br/> #S'il y-a une véritable séparation entre les routes, alors laisser la jonction telle que les deux côtés ne soient pas alignés <br /> [[Image: Jct_4_offset_ex.png]]. <br />(Les puces GPS peuvent être imprécises ce qui peut faire croire que le conducteur a sauté au-dessus d'un petit segment et se traduira par un "Map Problem" ou un recalcul d'itinéraire.)<br />Pour éviter les très petits segments de route, il peut être judicieux de décaler les routes le plus loin possible les unes des autres afin de maximiser la longueur du petit segment entre les routes.<br />[[Image:Jct_4_offset_sep_ex.png]] 659bdce9e9c5a290fe932444156d9c54417f2261 0 21 11174 11173 2016-06-19T20:37:22Z Wottem 21 1 Version importiert wikitext text/x-wiki #REDIRECT [[Tout sur les ronds-points]] 62ef853f734e63e7cad4d981469cf276c93dd99a 0 22 11185 11184 2016-06-19T20:37:23Z Wottem 21 10 Versionen importiert wikitext text/x-wiki {{France Tabs|Communauté}} {{Navigation rapide/Communauté}} Waze met en oeuvre un ensemble de mécanismes destinés à récompenser la contribution des utilisateurs à la communauté. Cela se traduit par une attribution de points qui vous positionnent dans un classement par rapport aux autres utilisateurs en France ou dans le monde. Les contributions à la communauté prennent essentiellement 2 formes * La conduite avec Waze avec la capture d'informations temps-réel sur le trafic et les événements que vous signalez * L'édition de la Carte {{:Points et Classement/Consulter ses points et son classement|transcludesection=CONTENT}} {{:Points et Classement/Comment sont attribués les points|transcludesection=CONTENT}} {{:Points et Classement/Classement général et Rangs|transcludesection=CONTENT}} 22e8e1c667b13f19942d413d1b82631bf84d1237 0 23 11224 11223 2016-06-19T20:37:28Z Wottem 21 38 Versionen importiert wikitext text/x-wiki [[Switzerland|Back to Wiki Switzerland]] =Road Classification= Here you can find the assignment and designation of roads and cities in Switzerland. * If you have any questions post here in this thread: [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Discussion-Thread]. * Languages: German, English, French, Italian, everybody is welcome. * Or [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM] me directly if you have any questions. =Map Legend Switzerland= Here you can find the [[Kartenlegende Schweiz|Map Legend Switzerland]] with informations on signage and the individual segments. =Road Categories= ==Highways== * <span style="color:RoyalBlue;">'''Freeway'''</span> => Freeways in Switzerland * <span style="color:RoyalBlue;">'''Major Highway'''</span> => Express roads which are not freeways * <span style="color:RoyalBlue;">'''Minor Highway'''</span> => Numbered main streets, max. two digits. * <span style="color:RoyalBlue;">'''Ramps'''</span> => Entrance and exit to freeways ==Streets== * <span style="color:RoyalBlue;">'''Primary Street'''</span> => Main streets with yellow roadshield * <span style="color:RoyalBlue;">'''Street'''</span> => Roads or secondary roads * <span style="color:RoyalBlue;">'''Service Road'''</span> => Are not used in CH. -> Merged in 2014 with road category 'street'. ==Other - drivable== * <span style="color:RoyalBlue;">'''Dirt Roads/4x4 Trails'''</span> => Gravel roads, field roads (agriculture and forestry), forest roads. * <span style="color:RoyalBlue;">'''Parking Lot Road'''</span> => All types of parking lots * <span style="color:RoyalBlue;">'''Private Road'''</span> => Private roads ==Non-drivable== * <span style="color:RoyalBlue;">'''Walking Trails'''</span> => Walking trails * <span style="color:RoyalBlue;">'''Pedestrian Boardwalk'''</span> => Pedestrian walkways, boardwalks, all kind of riverside walks * <span style="color:RoyalBlue;">'''Stairway'''</span> => Stairways * <span style="color:RoyalBlue;">'''Railroad'''</span> => Railroads * <span style="color:RoyalBlue;">'''Runway/Taxiway'''</span> => Runways/taxiways <br>(This is here for completeness. It makes no sense to equip all airports with these, Landmark (Airport) is quite sufficient!) ==Signage== Assignment of the main and secondary roads: * Please pay attention to the signage. ** Blue signpost, blue town sign, white/yellow square sign (main road) => Primary Street ** White signpost, white town sign (secondary road) => Street =Road naming= ==Freeways== Freeway => Freeway * Naming: A1, A2, A3 - E60... ==Express roads== Major Highway => Express roads * Naming A1L, A52... ==National main streets== Minor Highway => National main streets with a number, max. two digits. * Inner city: Streetname and "Alt Street" N1, N2... * Outer city: If there is no streetname: N1, N2...<br> If a National main street is leading over a freeway the name of the freeway and "Alt Street" N1, N2... ==Numbered main streets== Minor Highway => National-, and numbered main streets, max. two digits.<br> * Inner city: Streetname and "Alt Street" H1, H2... * Outer city: If there is no streetname: H1, H2... '''Please note: there are two different kind of numbered main roads in Switzerland! The N-type is mostly not in use anymore or is leading over the freeways.''' ==Exit ramps and Entrance ramps== Ramps => Ramps to and from freeways<br> Designation referred to the names on the signs of the entrances and exits.<br> The ">" is spoken by TTS as "Richtung" which means "direction to" <br> Exit * Ausfahrt Zürich Flughafen * Ausfahrt Bülach-Nord<br> Entrance * Einfahrt > Basel Bern Luzern * Einfahrt > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Einfahrt > Basel ===Freeway intersections=== Freeway intersections and exits, should be labelled with a landmark. The landmark should be kept tight to the road system to ensure a tidy transfer to the client. The landmark should be named with the number and the name of the intersection.<br>Type is: "Junction/Interchange". '''Example:''' "17 Frick" *[[Image:Frick.png|600px]] '''Example:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Streets== Streetnames according to the name on the road sign. =Cities= Make sure that a city name is unique and assign only names which have an on zip code! We have a list of all valid citynames here: [[Ortsliste Schweiz]] =Sources= *List of all freeways [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *List of all express roads (Major Highway)[http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *List of all national main roads (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *List of numbered main roads (Minor Highway) [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Back to Wiki Switzerland]] [[Category:Schweiz]] 45c1071524de3fac7bf4f4c033d59befb704e746 0 24 11226 11225 2016-06-19T20:37:28Z Wottem 21 1 Version importiert wikitext text/x-wiki #REDIRECT [[Road types and names]] 700adfe90ad01be478231919a3cf13bef309e5f5 0 25 11250 11249 2016-06-19T20:37:30Z Wottem 21 23 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] == '''Waze und was nun?''' == Nach der [[How to get the free Waze client|Installation]] von Waze hast du sicher ein paar Fragen. * Bitte wahre den Anstand im [[Diskussionsforum|Forum]]. * Alles was schon gesagt wurde findest du über die [http://www.waze.com/forum/search.php Foren Suche]. * Sieh im [[Main Page|Wiki]] nach. Länderspezifische Wikis sind ebenfalls vorhanden. * Lies die Seite über [[Häufig gestellte Fragen|Häufig gestellte Fragen]] oder die Seite über bereits bekannte [[Problems, bugs and limitations|Probleme]]. * Wenn du einen Post schreibst, verwende einen das Problem gut beschreibenden Titel. Grossschrift und Sonderzeichen sind nicht nötig! Bitte suche für Deine Frage das jeweils passende Unterforum, dies erspart den Admins unnützes Verschieben Deiner Beiträge in die richtige Kategorie. * Gebräuchliche Begriffe findest Du im [[Glossar]] * Falls es sich um Fragen des [[Client device|Clients]] resp. der Waze Applikation auf deinem Smartphone handelt, vergiss nicht Daten wie: Verwendetes Smartphone, Betriebssystem incl. Versionsnummer und installierte Wazeversion zu erwähnen. <br>Man darf diese Daten auch in die eigene Signatur packen: <br>''User Control Panel -> Profile -> Edit Signature'' * Lese die [[User Manual|Anleitung]] zu deinem Smartphone. * Gib bitte an in welchem Land du mit Waze unterwegs bist, so erübrigt sich die Frage auf welchem [[Die Server Bänke|Server]] du dich befindest:<br>''User Control Panel -> Profile, unter Location.'' * Schau die [[Mein Dashboard|Dashboard]] Seite an bevor du dazu eine Frage stellst. * Das Wiki mag an manchen Stellen nicht mehr Zeitgemäss sein, daher steht es dir frei als erfahrener Wazer mitzuhelfen das Wiki zu [[Hilf_mit_Waze_zu_verbessern#Aktualisiere_das_Wiki |aktualisieren]]. * Der Waze Staff ist nicht gross, die meisten Antworten erhältst du von anderen Wazern im Forum. Deshalb ist es wichtig, dass du dich an die oben erwähnten Vorschläge hältst. Es sind sonst nicht allzu viele Antworten zu erwarten. <br>Denn nach dem zwanzigsten Post mit Titeln wie: [[Ablauf der Aktualisierungsprozesse|"Meine Punkte oder Map-Edits wurden nicht aktualisiert"]] oder [http://www.waze.com/forum/search.php "Wieso sieht man keine Eisenbahnen"], wird nicht jeder gewillt sein zu antworten. * Du darfst natürlich auch [[Make suggestions to improve Waze|Vorschläge]] machen um Waze zu verbessern. <br> Wenn du dir nicht selbst helfen konntest, frage im Forum nach. <br> Wenn alles fehlschlägt und man dir im Forum nicht helfen konnte, verwende als erstes die [http://www.waze.com/support/ Seite "Benutzerunterstützung"]. Oder melde dich per [[Mail an den Support|Mail]] an Waze. <br>'''Weitere Informationen:''' * Warum sagt Waze im [[Erstellen_und_bearbeiten_eines_Kreisverkehrs#Navigationsanweisungen_verstehen|Kreisverkehr]] "Die erste Ausfahrt nehmen" oder "Rechts abbiegen?" * Warum sagt Waze beim [[How Waze determines turn / keep / exit maneuvers|Abbiegen]] "Rechts halten" oder "Rechts Abbiegen"? * Was is ein [[Der Area Manager|Area-Manager]]? * Teile deine [https://docs.google.com/spreadsheet/ccc?key=0AnK4ogNrUnhmdDM1LXIzNXNFblJMMkJRelo0NzR5dkE&hl=en_GB#gid=1 Kontakt Informationen] mit anderen AM und der Community. * Wie lauten die Adressen der [[RSS Feeds|RSS Feeds]] für Waze? <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 95ea7014fc3c41b40753028fd3931ea40eca804d 0 26 11267 11266 2016-06-19T20:37:31Z Wottem 21 16 Versionen importiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Hast Du nach einer Lösung gesucht?= Wenn du ein Problem hast, stelle sicher, dass Du [[Wann stelle ich ein Frage im Forum|hier]] nicht die Lösung gefunden hast! =Wichtige Daten= Wenn Du Fragen an Waze richtest, können folgende Angaben nötig sein: * Benutzername. * Telefon Model, OS und Version, verwendete Waze Version. * Bei Fragen zur Karte auf der Waze App kann auch ein Screenshot hilfreich sein. * Bei Fragen zur Karte im Karten-Editor ist ein [[Der Waze Map-Editor#Der Permalink|Permalink]] erforderlich, damit sich Waze dein Problem ansehen kann. * Bei Fragen zur Performance, welcher [[Die Server Bänke|Server]] betrifft es? =Problem Beschreibung= Beschreibe dein Problem genau, was Du erwartest und was tatsächlich passiert. * Kannst Du das Problem reproduzieren? * Kannst Du die Schritte beschreiben, die Du gemacht hast um ein Problem zu reproduzieren? Wenn ja, kann es Waze auch reproduzieren und dir wird geholfen. =Amtssprache= Wenn Du eine schnellere Antwort erhalten willst, bedenke, dass der Waze Support nicht in Deutsch kommuniziert. Deshalb ist es von Vorteil, dass Du dein Anliegen auf '''Englisch''' beschreibst. Wenn Du der Sprache nicht mächtig bist, kannst Du auch über das Forum oder per PM Hilfe anfordern von der Community. =Quick Help auf der Supportseite= Wenn Du dir über all das Gedanken gemacht hast, stelle deine Frage an den Support auf der [http://www.waze.com/support/ Seite "Benutzerunterstützung"]. [[Image:NanoRep-Box.png|center]] =Geduld= Der Waze Support antwortet nicht im Minuten Takt und muss priorisieren was zuerst erledigt werden soll, deshalb sei geduldig. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] a682246b43b6e89d59bd2abdb60193906a854dc7 0 27 11272 11271 2016-06-19T20:37:31Z Wottem 21 4 Versionen importiert wikitext text/x-wiki #REDIRECT [[Technical links]] b3a6c6293804cd9a6b767cfc6d2e166cfdc6b5e0 0 29 11395 11394 2016-06-19T20:38:13Z Wottem 21 12 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> == {{@|La barre d'outils}} == [[File : Barre d'outils WME.png | 600px]] En haut de la fenêtre de l'éditeur se trouve la barre d'outils. On y trouve une zone de recherche et les principaux boutons de contrôle de l'éditeur : Tracer, Sauvegarder, Annuler, Refaire, Supprimer et Calques {{Collapsible section top}} ===={{@|Zone de recherche}}==== {{Collapsible section content}} [[File : Zone de recherche.png | 300px | right]] On peut sélectionner la zone de recherche en appuyant sur la touche {{key press|F}}. Dans la zone de recherche, on peut entrer une adresse, un pays, une ville, un POI ou une combinaison de tout cela. Après envoi de la requête (en appuyant sur Entrée ou en cliquant sur le bouton Rechercher), vous obtenez une liste de résultats qui sont susceptibles de correspondre à votre recherche et parmi lesquels vous devrez choisir celui qui vous convient (voir l'exemple ci-contre). S'il n'y a pas d'équivoque possible dans votre recherche, vous n'aurez pas cette liste de choix et la Carte sera immédiatement centrée sur le résultat de cette recherche. {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|Bouton Tracer}} ==== {{Collapsible section content}} [[File : Menu Ajouter.png | right]] Le bouton ''Tracer'' n'est pas vraiment un bouton, mais un menu déroulant. Il n'est pas nécessaire de cliquer dessus, il suffit de le survoler avec la souris pour que son menu apparaisse. Il est également possible d'utiliser les [[#Raccourcis clavier | raccourcis clavier]] suivants : * {{key press|I}} - Route * {{key press|O}} - Rond-Point * {{key press|G}} - Station-service * {{key press|P}} - Parking * {{key press|Y}} - Lieu (point) * {{key press|U}} - Lieu (zone) Chacune de ces actions est détaillée dans le Guide d'Édition. {{Collapsible section bottom}} {{Collapsible section top}} ===={{@|Bouton Sauvegarder}}==== {{Collapsible section content}} <div style="float:right;">[[Image : wme31 button save.jpg]] [[File : wme31 button save pending.jpg]] [[File : wme31 button save pending red.jpg]]</div> Raccourci clavier : {{key press|Ctrl|S}} Le bouton Sauvegarder a deux utilités : # Afficher le nombre de modifications en attente de sauvegarde # Enregistrer toutes ces modifications, lorsqu'on clique dessus. Le compteur sur le bouton s'incrémente à chaque modification faite. Dès lors qu'il y a plus de 9 changements en attente, le texte sur le bouton passe en rouge pour vous avertir qu'il peut devenir plus difficile d’appliquer ces changements si une erreur s'y trouve. Lorsque le bouton est pressé (ou le raccourci clavier utilisé), WME enregistre tous les changements effectués. Si une erreur s'est produite pendant l'enregistrement, WME tentera de vous donner un message d'erreur détaillé ainsi qu'une suggestion pour la corriger. En règle générale, la vue sur la carte se déplace sur la zone posant problème (qui apparaît alors en surbrillance) . {{Red|Attention, il n'est plus possible de revenir en arrière une fois l'opération de sauvegarde validée.}} {{Collapsible section bottom}} {{Collapsible section top}} ===={{@|Bouton Annuler}}==== {{Collapsible section content}} <div style="float:right;">[[File : wme31 button undo.jpg]]</div> Raccourci clavier: {{key press|Ctrl|Z}} Le bouton ''Annuler'' permet d'annuler tout ou partie des modifications réalisées, '''non encore sauvegardées'''. {{Red|IMPORTANT: A partir du moment où vous cliquez sur Sauvegarder, si l'opération est validée (aucune erreur ne s'est produite), le bouton Annuler ne permettra plus de revenir en arrière.}} {{Collapsible section bottom}} {{Collapsible section top}} ===={{@|Bouton Refaire}}==== {{Collapsible section content}} <div style="float:right;">[[File : wme31 button redo.jpg]]</div> Raccourci clavier: {{key press|Ctrl|Shift|Z}} Le bouton ''Refaire'' ré-applique les changements qui ont été précédemment annulés avec le bouton ''Annuler''. {{Collapsible section bottom}} {{Collapsible section top}} ===={{@|Bouton Supprimer}}==== {{Collapsible section content}} <div style="float:right;">[[File : wme31 button delete.jpg]]</div> Raccourci clavier: {{key press|Suppr}} Le bouton ''Supprimer'' supprime tout objet sélectionné. Si vous avez sélectionné plusieurs objets (les seuls objets autorisant la suppression multiple étant les segments), une fenêtre de confirmation apparaîtra. Le bouton ''Annuler'' fonctionne sur les objets supprimés. Comme toute modification, les objets ne seront réellement supprimés qu'après sauvegarde des modifications avec impossibilité ensuite de revenir en arrière. Remarque : le raccourci clavier ( {{key press|Suppr}} ) ne fonctionne qu'avec un seul objet est sélectionné. Les suppressions multiples imposent de passer par le bouton ''Supprimer'' et de confirmer l'action. {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|Calques}} ==== {{Collapsible section content}} [[File : Menu Calques.png|right]] Le bouton des Calques permet, lorsque l'on passe la souris dessus, d'ouvrir un menu déroulant proposant tous les types de calques disponibles à l'affichage. Les cases cochées dans ce menu correspondent aux calques actifs et visibles. Il existe des raccourcis clavier, indiqués plus bas sur cette page, pour chacun d'entre eux. Les calques "Villes", "Routes" et "Traces GPS" disposent, dans la bordure gauche du menu, d'une poignée (sous la forme de 6 petits points) qui permet de déplacer l'ordre de ces calques, ce qui réorganise leur ordre de superposition. ATTENTION: Ce sont les calques en bas de la liste qui seront affichés en dernier, donc <u>par-dessus</u> les autres. Enfin, en haut à droite du menu déroulant, cette icône [[File : Reload Layers.png | 30px]] permet d'actualiser l'affichage des calques, ce qui permet de recharger les informations les plus récentes et dans certains cas de résoudre des bugs d'affichage. Cette méthode de rafraîchissement présente également l'avantage de ne pas réinitialiser toute l'interface WME et donc de ne pas perdre l'historique du Chat en cours. (raccourci clavier : {{key press|Alt|Shift|R}} ) {{Clear}} ===== Calque "Imagerie Satellite" ===== [[File : Aerial_skinny.png| 260px | right]] Raccourci clavier: {{key press|Shift|I}} Affiche une vue satellite de la zone concernée, permettant de visualiser la cohérence entre la cartographie et la réalité du terrain. Waze utilise une vue aérienne fournie par Google. Notez que cette vue est actualisée par Google avec des intervalles de temps assez long, ce qui peut conduire l'affichage d'une image qui n'est plus le reflet de la réalité du terrain. Pour éviter de montrer une vue satellite trop pixelisée, ce calque peut ne pas s'afficher si le niveau de zoom est trop élevé (vue trop détaillée) {{Clear}} ===== Calque "Villes" ===== [[File : cities_skinny.png | 260px | right]] Raccourci clavier: {{key press|Shift|C}} Les limites des villes, automatiquement définies par les segments portant le nom de la ville, apparaissent sous différentes couleurs. Ce calque est utile pour identifier les segments nommés de façon incorrecte (présence du nom de la ville loin de la zone urbaine, provoquant une extension anormale du polygone représentant la ville) {{Clear}} ===== Calque "Routes" ===== [[File : Calque Route.png | 260px | right]] Raccourci clavier: {{key press|Shift|R}} Les routes correspondent à l'ensemble des rues, allées, chemin, départementales, autoroutes... qui composent la totalité du réseau routier dans Waze. En fonction du Niveau de Zoom, les types de routes les moins importants n’apparaîtront pas pour éviter de surcharger la carte. {{Clear}} ===== Calque "Traces GPS" ===== [[File : Gps_tracks_straight_skinny.png | 260px | right]] Raccourci clavier: {{key press|Shift|G}} Ce calque affiche les coordonnées GPS des trajets effectués par les utilisateurs de Waze. Il est utile pour placer assez précisément les routes nouvelles ou modifiées lorsque la vue aérienne n'est pas encore à jour. Les points GPS apparaissent dans WME sous forme de flèches colorées, et cette couleur est déterminée par la direction du trajet. Cela permet de déterminer plus facilement les points GPS isolés, ou les routes ne correspondant pas au trajet réel des véhicules. Occasionnellement, vous pourrez trouver des traces GPS farfelues ou en décalage notable avec ce que vous connaissez de la réalité du terrain. Ceci provient généralement soit d'une imprécision soit d'un décrochage du signal GPS du terminal mobile utilisé. {{Clear}} ===== Calque "Gestionnaires de Zones" ===== [[File : Wme3 area managers layer skinny.png | 260px | right]] Raccourci clavier: {{key press|Shift|A}} Le calque Gestionnaires de Zones (ou Area Managers) affiche des rectangles colorés, contenant le nom d'un Area Manager (AM) et se superposant les uns les autres. Ces zones représentent les zones dans lesquelles chaque AM a des droits d'éditions. Ce calque permet d'identifier puis de contacter l'AM pour lui indiquer un problème que vous avez trouvé dans sa zone mais que vous ne pouvez résoudre car vous n'avez pas les droits nécessaires. Remarque : Le nom de l'Area Manager est affiché au centre de sa zone; Certaines zones étant très grandes, le nom n’apparaît pas toujours sur la portion de la carte que vous consultez. {{Clear}} ===== Calque "Lieux" ===== [[File : Calque Lieux.png | 260px | right]] Raccourci clavier: {{key press|Shift|L}} Les Lieux (encore appelés "points d’intérêts" ou POI) sont destinés à identifier les endroits notables sur la Carte. Généralement ils représentent des parcs, des églises, des mairies, des stations services, des cimetières, des stations de transports en commun, etc. Les Lieux d'intérêts apparaissent dans WME sous deux formes : * Des polygones violets, pour les Lieux déclarés sous la forme de '''zones'''. * Des ronds violets ( [[File : Wme place.png]] ), pour les Lieux déclarés sous la forme de '''points''' précis. {{Clear}} ===== Calque "Radars" ===== <div style="float:right">[[Image:Speed_cam_enabled.png]] [[Image:Red-light_cam_enabled.png]]</div> Raccourci clavier: {{key press|Shift|S}} Les radars de vitesse, les radars pédagogiques (informant de la présence d'un radar) et les radars feux rouges apparaissent sur ce calque. Voir le Guide d'Édition pour plus d'informations sur le bon usage des Radars. {{Clear}} ===== Calque "Problèmes de carte" ===== <div style="float:right">[[File : Problem pin open-low.png]] [[File : Problem pin open-med.png]] [[File : Problem pin open-high.png]]</div> Raccourci clavier: {{key press|Shift|P}} Les serveurs de Waze analysent en permanence les traces GPS des utilisateurs pour détecter les anomalies de circulation en regard des segments existants. Ces anomalies (routes manquantes, mauvais sens de circulation, interdiction de tourner...) s'affichent ensuite sur le calque ''Problèmes de carte'' pour alerter les éditeurs. Consultez l'article sur les ''Problèmes de carte'' pour apprendre comment traiter correctement ce type de situation. <div style="float:right">[[File : Problem pin not-identified.png]] [[File : Problem pin solved.png]]</div> Lorsqu'un problème de carte a été traité et résolu par un éditeur, il disparaît par défaut de l'affichage. Pour permettre de consulter les problèmes qui ont été récemment résolus, vous pouvez utiliser l'option '''Montrer les fermés''' présent sous le choix du calque ''Problèmes de carte''. Les problèmes de carte résolus sont de couleur verte. A l'inverse pour les masquer, utilisez l'option '''Cacher les fermés''' situé au même endroit. {{Clear}} ===== Calque "Demande de mise à jour" ===== <div style="float:right">[[File : Request pin open-low.png|left]][[File : Request_pin_open_conversation-low.png]] [[File : Request_pin_open_conversation-high.png]]</div> Raccourci clavier: {{key press|Shift|U}} Les demandes de mise à jour sont des signalements envoyés par les utilisateurs durant leur trajet ou depuis la LiveMap. Ces icônes indiquent l'emplacement précis où l'utilisateur a émis l'erreur. Sauf exception (proximité du domicile, autres raisons techniques,...), une partie du trajet effectué par l'utilisateur apparaît en vert, et si Waze était en mode navigation au moment de l'envoi de l'erreur, l'itinéraire fourni par Waze à l'utilisateur apparaîtra en violet avec le sens de circulation et les icônes correspondant aux instructions générées par la navigation. Consultez l'article sur les ''Update Requests'' pour apprendre comment traiter correctement ce type de situation. <div style="float:right">[[File : Request pin-notidentified.gif]] [[File : Request_pin_solved_conversation.png]]</div> Lorsqu'une demande de mise à jour a été traitée et résolue par un éditeur, elle disparaît par défaut de l'affichage. Pour permettre de consulter les demandes qui ont été récemment résolues, vous pouvez utiliser l'option '''Montrer les fermés''' présent sous le choix du calque ''Demande de mise à jour''. Les demandes résolues sont de couleur verte. A l'inverse pour les masquer, utilisez l'option '''Cacher les fermés''' situé au même endroit. Voir la page sur les Erreurs de carte pour plus d'information. {{Clear}} ===== Calque "Mises à jour des Places" ===== <div style="float:right">[[File : Wme placemarker updated details.png]][[File : Wme placemarker new photo.png]] [[File : Wme placemarker flagged.png]] [[File : Wme placemarker new.png ]]</div> Raccourci clavier: {{key press|Shift|P}} Les utilisateurs, à partir de leur application mobile, sont invités par Waze à participer à la déclaration de Lieux notables, soit en complétant les informations relatives aux lieux existants (nom, catégorie, horaires d'ouverture, etc.) soit en y adjoignant des photos prises à partir de leur terminal mobile, soit en créant directement un nouveau Lieu. Toutefois, ces mises à jours ne sont ni systématiquement, ni immédiatement reportées dans la Carte et doivent préalablement être validées ou confirmées par les éditeurs. Ce calque affiche l'ensemble des demandes de mises à jour de Lieux (appelés "Places" sur l'application) en attente de validation. Voir la page sur le traitement des Demandes de mises à jour des Lieux pour plus d'information. {{Clear}} ===== Calque "Zones modifiables" ===== [[File : Editable_area_skinny.png | 260px | right]] Raccourci clavier: {{key press|Shift|E}} La zone modifiable est déterminée principalement par les trajets effectués avec Waze actif. Les droits de modification sur la carte sont accordés dans un rayon donné autour de ces trajets. Les zones qui ne vous sont pas accessibles en modification apparaissent assombries quand ce calque est actif. Votre zone d'édition autorisée, quant à elle, apparaît normalement. Voir le Guide d'Edition pour plus d'informations. {{Clear}} ===== Calque "Live Users" ===== [[File : Live user.png | 260px | right]] Raccourci clavier: {{key press|Shift|V}} Ce calque affiche sur la Carte les éditeurs actuellement connectés qui travaillent sur la zone affichée. Ils sont représentés sous la forme de l'icône ci-contre. Leur présence signifie qu'ils sont peut être en train de faire des modifications à cet endroit. Aussi est-il prudent, avant d'entamer vos travaux, de contacter l'utilisateur en question sur le Chat, pour vous coordonner avec lui. {{Clear}} {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> 3b09808578afd2b3f6016c172512983798e09d13 0 30 11402 11401 2016-06-19T20:38:15Z Wottem 21 6 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> {{Collapsible section top}} == {{@|Raccourcis clavier}} == Il existe un ensemble de raccourcis clavier, disponible lorsque vous utilisez WME, vous permettant de réaliser les actions les plus courantes de manière rapide, surtout si vous préférez l'utilisation du clavier à celle de la souris. {{Collapsible section content}} ===== Personnalisation des raccourcis ===== Vous trouverez ci-dessous, les raccourcis clavier par défaut. Vous pouvez personnaliser certains de ces raccourcis clavier en affichant la fenêtre d'aide sur les raccourcis (en bas de la zone d'onglets ou en utilisant la touche {{key press|?}}. Sélectionnez en un et appuyez ensuite sur la touche (ou combinaison de touches avec {{key press|Shift}}, {{key press|Alt}},...) de votre clavier que vous souhaitez utiliser en remplacement du raccourci par défaut. Ceci n'a d'effet que sur le navigateur utilisé et sur l'ordinateur utilisé (les raccourcis personnalisés ne sont pas stockés sur le serveur, donc vous devrez répéter l'opération sur chaque ordinateur et chaque navigateur que vous utiliserez). ===== Liste des raccourcis par défaut ===== <table class="wikitable unsortable" border="1"> <tr> <th width="120" style="background:#A9A9A9; color:white; border:solid 1px #DCDCDC;">Raccourci</th> <th width="480" style="background:#A9A9A9; color:white; border:solid 1px #DCDCDC;">Description</th> </tr><tr style="background:#DCDCDC; color:black"> <td colspan="2" rowspan="1" style="text-align: center;">'''General'''</td> </tr><tr> <td>{{key press|F}}</td> <td>Sélectionne la [[#zone de recherche| zone de recherche dans la barre d'outils]]</td> </tr><tr> <td>{{key press|?}}<br/>{{key press|Shift|/}}<br/>{{key press|Shift|-}}<br/>{{key press|Shift|~}}<br/>{{key press|Shift|ù}}</td> <td>Affiche la fenêtre des raccourcis clavier</td> </tr><tr> <td>{{key press|Ctrl|S}}</td> <td>[[#Bouton Sauvegarder|Sauvegarde]] les modifications réalisées</td> </tr><tr> <td>{{key press|Delete}}</td> <td>[[#Bouton Supprimer|Supprime]] l'objet <u>unique</u> sélectionné (segment, intersection, Lieu). Pour supprimer plusieurs objets selectionnés, vous devez utiliser le [[#Bouton Supprimer|bouton ''Supprimer'' (Corbeille)]] situé dans la barre d'outils et confirmer la suppression multiple.</td> </tr><tr> <td>{{key press|Esc}}</td> <td>Désélectionne tous les objets</td> </tr><tr> <td>{{key press|Alt|Shift|R}}</td> <td>Actualise l'affichage de tous les calques visibles (rafraîchissement de l'affichage sans utiliser un permalien, ce qui préserve l'historique de la fenêtre de Chat)</td> </tr><tr style="background:#DCDCDC; color:black"> <td colspan="2" rowspan="1" style="text-align: center;">'''Ajout d'objets'''</td> </tr><tr> <td>{{key press|G}}</td> <td>Ajoute une nouvelle Station Essence</td> </tr><tr> <td>{{key press|I}}</td> <td>Ajoute un nouveau segment de route</td> </tr><tr> <td>{{key press|O}}</td> <td>Ajoute un nouveau rond-point</td> </tr><tr> <td>{{key press|P}}</td> <td>Ajoute une nouvelle zone de stationnement (parking)</td> </tr><tr> <td>{{key press|U}}</td> <td>Ajoute une nouveau Lieu notable sous la forme d'une zone</td> </tr><tr> <td>{{key press|Y}}</td> <td>Ajoute une nouveau Lieu notable sous la forme d'un point précis</td> </tr><tr style="background:#DCDCDC; color:black"> <td colspan="2" rowspan="1" style="text-align: center;">'''Edition des segments'''</td> </tr><tr> <td>{{key press|D}}</td> <td>Supprime le noeud de géométrie situé sous le pointeur de la souris</td> </tr><tr> <td>{{key press|E}}</td> <td>Lorsqu'au moins un segment est sélectionné, cela active le mode édition de l'adresse (pays, ville, rue) du ou des segments</td> </tr><tr> <td>{{key press|H}}</td> <td>Lorsqu'un seul segment est sélectionné, cela active le mode édition des numéros de rue de ce segment</td> </tr><tr> <td>{{key press|M}}</td> <td>Active ou désactive le mode de multi-sélection. Par défaut, pour sélectionner plusieurs segments, vous devez maintenir appuyé la touche {{key press|Ctrl}}. Quand ce mode est actif, chaque sélection d'un nouveau segment s'ajoute à la précédente sélection sans avoir à maintenir la touche {{key press|Ctrl}} appuyée.</td> </tr><tr> <td>{{key press|R}}</td> <td>Change le sens de circulation des segments sélectionnés pour, successivement, chacun de ces choix : Sens unique (A->B), Sens unique (B->A) et Double-sens (↔).Ne fonctionne que si tous les segments sélectionnés ont le même sens de circulation</td> </tr><tr> <td>{{key press|T}}</td> <td>Lorsqu'au moins un segment est sélectionné, affiche la boite de dialogue pour le paramétrage des restrictions programmées</td> </tr><tr> <td>{{key press|Ctrl|A}}</td> <td>Sélectionne toute la rue : Lorsqu'un segment est sélectionné (ou plusieurs segments de la même rue), ce raccourci étend la sélection l'ensemble des segments qui composent cette rue (en se basant sur le nom de la rue et le nom de la ville)</td> </tr><tr> <td>{{key press|Ctrl|Z}}</td> <td>[[#Bouton Annuler|Annule]] la dernière modification non encore sauvegardée</td> </tr><tr> <td>{{key press|Ctrl|Shift|Z}}<br />{{key press|Ctrl|Shift|Y}}</td> <td>[[#Bouton Refaire|Refait]] la modification qui vient d'être annulée</td> </tr><tr> <td>{{key press|Ctrl|Up}}</td> <td>Augmente l'élévation du segment sélectionné (ou des segments <u>de même élévation</u> sélectionnés)</td> </tr><tr> <td>{{key press|Ctrl|Down}}</td> <td>Diminue l'élévation du segment sélectionné (ou des segments <u>de même élévation</u> sélectionnés)</td> </tr><tr style="background:#DCDCDC; color:black"> <td colspan="2" rowspan="1" style="text-align: center;">'''Intersections et Flèches'''</td> </tr><tr> <td>{{key press|A}}</td> <td><div style="float:right;">[[File:ArrowTrans1.png|100px]]<br /><br />[[File:ArrowTrans2.png|100px]]</div>Alterne l'affichage transparent ou opaque des flèches de changement de direction (autorisation/interdiction) de manière que vous puissiez cliquer sur des objets situés en dessous d'elles. Souvent les éditeurs débutants tapent par mégarde sur la touche {{key press|A}} et s'étonnent de ne plus pouvoir sélectionner ces flèches.</td> </tr><tr> <td>{{key press|Q}}</td> <td>Interdit tous les changements de direction au niveau de l'intersection préalablement sélectionnée, ce qui passe toutes les flèches de changement de direction au rouge</td> </tr><tr> <td>{{key press|W}}</td> <td>Autorise tous les changements de direction au niveau de l'intersection préalablement sélectionnée, ce qui passe toutes les flèches de changement de direction au vert. (Pensez à consulter l'article sur les "Soft Turn".)</td> </tr><tr> <td>{{key press|S}}</td> <td><div style="float:right;">[[File:ArrowSpread2.png|100px|right]]<br /><br />[[File:ArrowSpread1.png|100px|right]]</div>Active ou désactive l'affichage distinct des flèches d'autorisation/interdiction de changement de direction. L'affichage distinct décale l'affichage des flèches de manière à ce qu'elles ne se chevauchent pas, permettant ainsi de les sélectionner plus facilement.</td> </tr><tr> <td>{{key press|Shift|Z}}</td> <td><div style="float:right;">[[File:ArrowShowAll1.png|100px|right]]<br /><br />[[File:ArrowShowAll2.png|100px|right]]</div>Active ou désactive l'affichage de TOUTES les flèches d'interdiction de changement de direction (rouges) existantes sur l'ensemble des segments présent dans la zone d'affichage de la carte. Si ce mode est actif, aucune flèche verte ne s'affiche.</td> </tr><tr style="background:#DCDCDC; color:black"> <td colspan="2" rowspan="1" style="text-align: center;">'''Affichage et Calques'''</td> </tr><tr> <td>{{key press|Shift|A}}</td> <td>Affiche ou masque le calque des Area Managers</td> </tr><tr> <td>{{key press|Shift|C}}</td> <td>Affiche ou masque le calque des Villes</td> </tr><tr> <td>{{key press|Shift|E}}</td> <td>Affiche ou masque le calque des Zones Modifiables</td> </tr><tr> <td>{{key press|Shift|F}}</td> <td>Active ou désactive le mode plein-écran</td> </tr><tr> <td>{{key press|Shift|G}}</td> <td>Affiche ou masque le calque des Traces GPS</td> </tr><tr> <td>{{key press|Shift|I}}</td> <td>Affiche ou masque le calque de l'Imagerie Satellite</td> </tr><tr> <td>{{key press|Shift|L}}</td> <td>Affiche ou masque le calque des Lieux notables (zones et points)</td> </tr><tr> <td>{{key press|Shift|V}}</td> <td>Affiche ou masque le calque des Live Users</td> </tr><tr> <td>{{key press|Shift|P}}</td> <td>Affiche ou masque le calque de mise à jour des Places</td> </tr><tr> <td>{{key press|Shift|R}}</td> <td>Affiche ou masque le calque des Routes</td> </tr><tr> <td>{{key press|Shift|S}}</td> <td>Affiche ou masque le calque des Radars</td> </tr><tr> <td>{{key press|Shift|U}}</td> <td>Affiche ou masque le calque des Demande de mise à jour (Update Requests)</td> </tr><tr> <td>{{key press|Shift|U}}</td> <td>Affiche ou masque le calque des Update Requests (Demande de mise à jour)</td> </tr><tr> <td>{{key press|Shift|W}}</td> <td>Ferme la fenêtre Streetview</td> </tr><tr> <td>{{key press|Alt|C}}</td> <td>Affiche ou masque la fenêtre du Chat</td> </tr><tr> <td>{{key press|Alt|Shift|R}}</td> <td>Actualise l'affichage de tous les calques visibles (rafraîchissement de l'affichage sans utiliser un permalien, ce qui préserve l'historique de la fenêtre de Chat)</td> </tr><tr> <td>{{key press|Shift|Up}}</td> <td>Augmente le Zoom sur l'affichage</td> </tr><tr> <td>{{key press|Shift|Down}}</td> <td>Diminue le Zoom sur l'affichage</td> </tr><tr> <td>{{key press|Up}}{{key press|Down}}{{key press|Left}}{{key press|Right}}</td> <td>Déplace la carte dans les 4 directions</td> </tr> </table> {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> a04d42acfc863477f3069be6a56d0d79dc39ca72 0 31 11408 11407 2016-06-19T20:38:16Z Wottem 21 5 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> {{Collapsible section top}} == {{@|S’authentifier sur WME}} == Vous obtenez un écran (ci-dessous) destiné à vous authentifier sur WME afin que les modifications que vous allez entreprendre soient bien associées à vous, sur les zones où vous disposez des droits pour le faire et avec les prérogatives associées à votre rang d’édition. {{Collapsible section content}} [[File : WME logon screen FR.png | 650px]] En dehors des zones de saisies destinées à votre pseudo Waze et votre mot de passe, cet écran d’accueil propose 4 rubriques intéressantes : [[File : Allons-y.png | 120px | right]] ==== Une vidéo d’introduction à l’édition ==== La première rubrique, « Allons-y », propose une série de petites vidéos de présentation et d’introduction à l’usage de l’interface WME. Il s’agit d’une vue très globale essentiellement destinée à présenter le système d'édition de Waze et la facilité d’usage de cette interface. Cependant les vidéos n’abordent pas les règles en vigueur, les bonnes pratiques et les aspects plus techniques de l’édition, qui sont justement traités de manière détaillée et approfondie dans ce wiki. {{clear}} [[File : Wiki de la communauté.png | 120px | right]] ==== Un lien vers ce Wiki ==== Il s’agit d’un lien vers la section Française du Wiki de la communauté Waze, c’est-à-dire la page d’accueil du wiki dont vous être en train de lire un article. {{clear}} [[File : Forums FR.png | 120px | right]] ==== Un lien vers les forums en anglais sur WME ==== Il s’agit, pour le moment, d’un lien vers les rubriques consacrées à WME sur le forum officiel de Waze, en anglais. Compte tenu des spécificités régionales et locales, les discussions générales qui ont lieu dans ces forums ne sont pas toujours applicables au contexte français. C’est pour cela qu’il convient plutôt d’utiliser le [http://www.waze.com/forum/viewforum.php?f=34 Le Forum Français de Waze]. {{clear}} [[File : Mode entrainement.png | 120px | right]] ==== Le Mode Entrainement de WME ==== Ce mode permet aux éditeurs débutants de pratiquer les fonctions d’édition de l’interface de WME, sans risquer d’endommager effectivement la Carte puisque aucune des modifications réalisées ne sera enregistrée. Il s’agit d’une fonctionnalité très utile pour faire ses premiers pas, en toute confiance, et sans risque, en particulier lorsqu’on souhaite tester une nouvelle fonctionnalité (par exemple, créer son premier rond-point) et qu’on ignore encore comment l’interface WME réagit à tel ou tel clic de souris ou action spécifique. {{clear}} {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> 84e2c0e3468c008180a27d96fa304539a90aa774 0 32 11415 11414 2016-06-19T20:38:17Z Wottem 21 6 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> {{Collapsible section top}} =={{@|Se déplacer sur la carte}}== Vous disposez de plusieurs solutions pour déplacer, zoomer et cadrer la carte sur la zone qui vous intéresse : {{Collapsible section content}} * Déplacez vous sur la carte en cliquant et glissant (clic & drag) sur ​​la carte elle-même * Utilisez les touches fléchées du clavier ( {{key press|Up}} {{key press|Down}} {{key press|Left}} {{key press|Right}} ) * Le raccourci clavier {{key press|Shift|F}} permet de masquer le bandeau Waze situé en haut de l'écran et mettre l'éditeur en mode "plein écran" Il y a cinq façons de zoomer sur la carte: # Avec la commande de zoom sur le coin supérieur gauche de la carte. Vous pouvez faire glisser le curseur (vers le haut ou vers le bas), ou cliquer sur les boutons '''+''' et '''-'''. # En utilisant les raccourcis claviers : {{key press|Shift|Up}} et {{key press|Shift|Down}} # En double-cliquant sur n'importe quel point sur ​​la carte, le zoom descendra d'un niveau et centrera la carte sur ce point. # En utilisant la molette de votre souris (molette-haut augmente le zoom et molette-bas le diminue). # En tenant la touche {{key press|Shift}} enfoncée, sélectionnez une zone sur la carte. L'affichage s'ajustera sur la zone sélectionnée. [[File : Zoom drag drop.png | 500px | center]] {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> a89cf4b2c03b94eebbbccd8e6e67cefc27b084e8 0 33 11425 11424 2016-06-19T20:38:19Z Wottem 21 9 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> =={{@|Zone d'affichage de la carte}}== Tous les calques sélectionnés dans le menu correspondant (voir [[#Calques|plus haut]]) apparaissent dans la zone d'affichage de la carte. Tous les objets visibles à l'écran sont sélectionnables. Cependant ils ne peuvent être modifiés que si vous avec les droits d'édition nécessaires. Il y a sept zones de contrôle/d'affichage sur la carte: [[File : Zone Affichage Carte.png | 600px]] {{Collapsible section top}} ==== {{@|Zone d'information}} ==== {{Collapsible section content}} <div style="float:right">[[File : Zone Info - Ville.png | 150px]]<br /><br /> [[File : Zone Info - Chargement.png | 150px]]</div> * On retrouve à gauche l'indication du lieu où l'on se trouve (ville et pays). * A droite, l'éditeur nous informe de l'état de chargement des calques (routes, points GPS, imagerie satellite, etc...). {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|Contrôle du zoom}} ==== {{Collapsible section content}} [[File : Zoom_controller.png | right]] Raccourci clavier: {{key press|Shift|Up}} et {{key press|Shift|Down}} Utilisation possible de la molette de la souris. Dans le coin supérieur gauche, la commande de zoom est un moyen de régler le niveau de zoom de la zone d'affichage de carte. En cliquant sur '''+''' vous affichez davantage de détails. Cliquer sur '''-''' provoque un zoom arrière et affiche moins de détails. Vous pouvez également cliquer et faire glisser le sélecteur situé sur la règle graduée entre les boutons '''+''' et '''-'''. {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|StreetView}} ==== {{Collapsible section content}} [[File : Wme sv lens blue.gif | right]] Pour activer StreetView, faites glisser l'icône de lentille bleue sur la rue pour laquelle vous souhaitez obtenir les images StreetView de Google. Lorsque vous faites glisser la lentille autour de la carte, elle change de couleur pour indiquer la présence ou non de vue StreetView : *[[Image:waze_sv_noview.gif]] StreetView non-disponible *[[Image:waze_sv_viewavail.gif]] StreetView disponible [[File : Wme streetview directional arrow.gif | right]] Une fois la lentille déposée sur une rue de la carte où StreetView est disponible, son icône se retrouve munie d'une flèche à l'intérieur qui pointe dans la direction de la vue. [[File : StreetView Garnier.png | 500px]] En mode StreetView, toutes les opérations d'édition sont disponibles (propriétés du segment, la carte des problèmes et des demandes de mise à jour, numéros de maison, les restrictions prévues, etc) et le côté droit de la zone d'affichage est maintenant dédié à StreetView. Vous pouvez déplacer l'image dans toutes les directions en faisant glisser l'image avec la souris ou en utilisant les commandes de déplacement en haut à gauche de la fenêtre. La fonction Zoom est également disponible à cet endroit. Pour se déplacer dans StreetView, utilisez soit les flèches qui apparaissent sur ​​l'image de StreetView au milieu et en bas. Ou vous pouvez faire glisser la lentille sur la carte Waze à l'aide de la petite poignée blanche présente sur l'icône. Bien que toutes les fonctions d'édition soient disponibles, l’affichage de trop de fonctions (StreetView, fenêtre de Chat, les problèmes de carte ou les demandes de mises jour) réduira considérablement la zone modifiable, à moins d'avoir un très grand écran. Notez également que la vue streetview peut dater et ne plus refléter la réalité du terrain. Pour <u>fermer StreetView</u>, ''cliquer'' sur le '''X''' dans le coin supérieur gauche de sa fenêtre, ou utilisez le raccourci {{key press|Shift|W}} {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|Échelle}} ==== {{Collapsible section content}} [[File : echelle.png | right]] Dans le coin inférieur droit se trouve un petit graphique montrant l'échelle actuelle de la zone d'affichage de carte. Dans le tableau ci-contre, les valeurs d'échelle correspondent au niveau de zoom que l'on retrouve dans l'adresse URL (adresse du site) du navigateur. Modifier le niveau de zoom modifie l'échelle affichée. <table class="wikitable" style="background:none; text-align:center; margin: 1em auto 1em auto" border="1"> <tr> <th>Niveau de Zoom</th> <th>Echelle (en mètres)</th> </tr> <tr> <td>10</td> <td>2</td> </tr> <tr> <td>9</td> <td>5</td> </tr> <tr> <td>8</td> <td>10</td> </tr> <tr> <td>7</td> <td>10</td> </tr> <tr> <td>6</td> <td>20</td> </tr> <tr> <td>5</td> <td>100</td> </tr> <tr> <td>4</td> <td>100</td> </tr> <tr> <td>3</td> <td>200</td> </tr> <tr> <td>2</td> <td>500</td> </tr> <tr> <td>1</td> <td>1000</td> </tr> </table> {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|Latitude/Longitude}} ==== {{Collapsible section content}} Dans le coin inférieur droit est affiché la latitude et la longitude du pointeur de la souris sur la carte. {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|Permalien}} ==== {{Collapsible section content}} [[File : bouton_permalink.png | right]] A droite de l'affichage Latitude / Longitude se trouve l'icône de création de '''Permalien''' (ou ''Permalink'' en anglais, souvent abrégé '''PL''' sur le forum ou sur le Chat). {{Clear}} Dans l'éditeur, un permalien est une URL utilisée pour amener quelqu'un directement à un endroit spécifique sur la carte. Cette URL contient les informations de latitude, longitude, niveau de zoom, calques visibles, ainsi que tous les objets (routes, jonction, Lieu ou UR) sélectionnés au moment où le permalien a été généré. Pour créer un permalien, commencez par régler le niveau de zoom, puis sélectionnez le ou les éléments que vous souhaitez montrer aux autres utilisateurs ({{key press|Ctrl}} + Clic gauche permet de sélectionner plusieurs segments à la fois). Passer ensuite votre souris sur l'icône Permalien, sans cliquer, et utiliser le raccourci {{key press|Ctrl|C}} lorsqu'apparaît une info-bulle vous proposant de le faire. Toutefois, la création de permaliens est soumise à quelques restrictions : * On peut sélectionner plusieurs segments mais un seul lieu ou jonction, * Les objets sélectionnés doivent être à l'écran, même partiellement, au moment de la génération du permalien, donc attention à vos déplacements de carte lors de la sélection, * Il n’est pas possible de créer un permalien pour les UR et MP. Si vous voulez partager un permalien, il vous faudra en créer un sans ces objets, * Les emails de réponse à une conversation dans une UR contiennent un permalien comprenant l’objet. Vous pouvez le partager. Seules les personnes ayant des droits d’édition à son emplacement pourront le voir. Pour les 2 derniers points, afin de rendre votre problème visible auprès du plus grand nombre, il vous faudra fournir des informations complémentaires (capture d'écran par exemple). {{Collapsible section bottom}} {{Collapsible section top}} ==== {{@|Chat}} ==== {{Collapsible section content}} [[File : WME Chat.png | right]] Cet icône permet d'afficher ou de masquer la fenêtre de Chat (messagerie instantanée) intégrée à l'interface de Waze Map Editor. Elle vous permet de dialoguer avec les éditeurs actuellement connectés et, par exemple, obtenir de l'aide en direct. Consultez l'article sur le Chat pour découvrir les détails de cet outil. {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> 0636215e4f868445c3c2ed4e20bcb2cfda4bdd3d 0 34 11430 11429 2016-06-19T20:38:19Z Wottem 21 4 Versionen importiert wikitext text/x-wiki {{France Tabs|Edition}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> =={{@|Zone d'onglets}}== Dans la partie gauche de la fenêtre, sous votre nom, se trouve une zone d'information générale contenant des onglets. Lorsque vous sélectionnez un ou plusieurs objets (segment, intersection ou Lieu), cette zone change pour vous permettre l’édition ou la visualisation des informations de ces éléments. Enfin, certains scripts (utilisables sous forme d'extension Chrome ou Firefox) ajoutent des onglets supplémentaires destinés à la gestion de leurs fonctionnalités propres. ===={{@|Onglets visibles par défaut}}==== [[File : Zone Onglets.png | 200px | right]] Quand aucun objet n'est sélectionné, seules les informations vous concernant sont affichées. Elles sont regroupées sous 3 onglets : {{Collapsible section top}} # Onglet '''Moi''' # Onglet '''Trajets''' # Onglet '''Zones''' {{Clear}} {{Collapsible section content}} =====Onglet Moi===== <div style="float:right">[[File : Wazer WME.png]][[File : permission_levels.png]]</div> L'onglet ''Moi'' affiche vos points et votre Rang d'édition: L'icone de Wazer avec un casque indique que vous avez des droits d'édition. A sa droite, les cônes de chantier avec un numéro correspondent à votre rang d'édition. En dessous se trouve un court texte détaillant votre rang et vos permissions. =====Onglet Trajets===== L'onglet ''Trajets'' vous permet de voir l'historique des trajets que vous avez effectué avec Waze lors des 3 derniers mois. En cliquant sur l'un d'entre eux, la carte va tenter de vous afficher au mieux le parcours choisi. Les trajets de plus de 40 km ne tiennent généralement pas intégralement à l'écran à cause des limitations au niveau du zoom. Les parties de trajet apparaissant en rouge correspondent soit à des routes inexistantes dans Waze (auquel cas vous pouvez zoomer sur la zone en question pour déterminer si la route doit être ajoutée) soit à la perte du signal GPS (dans un tunnel par exemple). Ces trajets ont un effet direct sur vos zones d'éditions puisque vous n'êtes habilités à modifier la carte que dans un rayon précis (dépendant de votre rang d'édition) autour de vos trajets effectués. =====Onglet Zones===== Cet onglet affiche vos zones d'édition, zones dans lesquelles vous pouvez effectuer des modifications. {{Collapsible section bottom}} ===={{@|Informations visible avec un/des segment(s) sélectionné(s)}}==== <div style="float:right">[[File : Onglet Segment.png | 200px]]</div> Lorsqu’on sélectionne un ou plusieurs objets (segment, intersection, Lieu), la Zone d’onglets laisse place aux propriétés de ces éléments. En premier lieu, on trouve le nombre d'objets sélectionnés, puis leurs informations. L'image ci-contre montre les informations visibles lorsque plusieurs segments sont sélectionnés. Des détails sur ces paramètres peuvent être trouvés sur le Guide d'Edition. {{Clear}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> c7364521bd8f3815aa5d5b1a3996432e88ccb4b6 10 35 11453 11452 2016-06-19T20:38:21Z Wottem 21 22 Versionen importiert wikitext text/x-wiki <includeonly><span id="{{{1|}}}">{{{1|}}}</span> {{anchor|.7B.7B.40.7C{{{1|}}}.7D.7D|{{{2|}}}}}[[File:Link.png|12px|text-top|link={{FULLPAGENAME}}#{{#if:{{{2|}}}|{{{2}}}|{{{1|}}}}}|link to this section]]{{#if:{{{edit|}}}|{{nbsp}}<div class="mw-editsection plainlinks">[[File:Edit.png|15px|baseline|link={{fullurl:{{{edit}}}|action=edit}}|edit]]</div>}}</includeonly><noinclude> {{documentation}} </noinclude> 6bc08d9ca26fe4fc2e61993e2110cdbf02d2e2e8 10 36 11463 11462 2016-06-19T20:38:22Z Wottem 21 9 Versionen importiert wikitext text/x-wiki {{#if:{{{1|}}}|<span id="{{{1|}}}"></span>}}<!-- -->{{#if:{{{2|}}}|<span id="{{{2|}}}"></span>}}<!-- -->{{#if:{{{3|}}}|<span id="{{{3|}}}"></span>}}<!-- -->{{#if:{{{4|}}}|<span id="{{{4|}}}"></span>}}<!-- -->{{#if:{{{5|}}}|<span id="{{{5|}}}"></span>}}<!-- -->{{#if:{{{6|}}}|<span id="{{{6|}}}"></span>}}<!-- -->{{#if:{{{7|}}}|<span id="{{{7|}}}"></span>}}<!-- -->{{#if:{{{8|}}}|<span id="{{{8|}}}"></span>}}<!-- -->{{#if:{{{9|}}}|<span id="{{{9|}}}"></span>}}<!-- -->{{#if:{{{10|}}}|<span id="{{{10|}}}"></span>}}<!-- -->{{#if:{{{11|}}}|<span class="error">Error in [[Template:Anchor]]: too many anchors, maximum is 10.</span>}}<noinclude> {{Documentation}} <!-- PLEASE ADD CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --> </noinclude> 07e11cee92129ba0f450efd7e0e28c94fb968cbb 10 37 11466 11465 2016-06-19T20:38:22Z Wottem 21 2 Versionen importiert wikitext text/x-wiki <includeonly>-moz-border-radius: {{{1|8px}}}; -webkit-border-radius: {{{1|8px}}}; border-radius: {{{1|8px}}};</includeonly><noinclude> <!-- ADD CATEGORIES AND INTERWIKIS TO THE /doc PAGE, NOT HERE, THANKS --> {{documentation}} </noinclude> af4350db0626148ae24dd33131e6291b623f4945 10 38 11469 11468 2016-06-19T20:38:22Z Wottem 21 2 Versionen importiert wikitext text/x-wiki <includeonly>-moz-box-shadow: {{{1|4px}}} {{{2|4px}}} {{{3|4px}}} {{{4|#CCC}}}; -webkit-box-shadow: {{{1|4px}}} {{{2|4px}}} {{{3|4px}}} {{{4|#CCC}}}; box-shadow: {{{1|4px}}} {{{2|4px}}} {{{3|4px}}} {{{4|#CCC}}};</includeonly><noinclude> <!-- ADD CATEGORIES AND INTERWIKIS TO THE /doc PAGE, NOT HERE, THANKS --> {{documentation}} </noinclude> 1f26926e3b1ad5bb5e0ed09f9a1ac2a9a1d47997 10 39 11477 11476 2016-06-19T20:38:23Z Wottem 21 7 Versionen importiert wikitext text/x-wiki <div style="clear:{{{1|both}}};"></div><noinclude>{{doc}}</noinclude> 15e943687be5d8f8e27fa6cc7813bbfa85df72a9 10 40 11482 11481 2016-06-19T20:38:23Z Wottem 21 4 Versionen importiert wikitext text/x-wiki <includeonly>{{Clear}}</div></div></includeonly><noinclude>{{Documentation|Template:Collapsible section top/doc}}</noinclude> a20a051d630eb44ed9b044c9e4fb33aa28066588 10 41 11485 11484 2016-06-19T20:38:23Z Wottem 21 2 Versionen importiert wikitext text/x-wiki <includeonly><div class="mw-collapsible-content"></includeonly><noinclude>{{Documentation|Template:Collapsible section top/doc}}</noinclude> 25937eec9d4b10f47792445ebed9575d6b2f48c4 10 42 11495 11494 2016-06-19T20:38:24Z Wottem 21 9 Versionen importiert wikitext text/x-wiki <includeonly><div class="toccolours mw-collapsible {{#ifeq:{{{expand}}}|yes||mw-collapsed}}" style="width:100%; border: hidden; background-color: transparent {{#if:{{{style|}}}|;{{{style}}}}}"></includeonly><noinclude>{{Documentation}}</noinclude> ce497271d80044641f2e9123325c1b4a4c48d834 10 43 11519 11518 2016-06-19T20:38:26Z Wottem 21 23 Versionen importiert wikitext text/x-wiki __NOTOC____NOEDITSECTION__{{Tab top | Tab-1 = Accueil | URL-1 = France | Image-1 = French_Flag_Icon.png | Tab-2 = Application | tab align-2=right | URL-2 = Applications Waze | Image-2 = Waze.png | Tab-3 = Edition | URL-3 = Edition de la Carte | Image-3 = Map_editing.png | Tab-4 = Communauté | tab align-4=right | URL-4 = Communauté Waze | Image-4 = Communauté.png | Tab-5 = Support | URL-5 = Support et Assistance | Image-5 = Help.png | rounding = 15 | asym = 4 | frame background = #FBFDFD | image size = 30px | font size = 91% | selected = {{{1|}}} }} <noinclude>{{Tab bottom}}{{Documentation}}</noinclude> <includeonly>[[Category:France]]</includeonly> 9e74acb742835abc75aeff1562c27a7e019ba735 10 44 11522 11521 2016-06-19T20:38:26Z Wottem 21 2 Versionen importiert wikitext text/x-wiki {{key press/core|{{{1|}}}}}<!-- -->{{#if:{{{2|}}}|{{{chain first|{{{chain|+}}}}}}{{key press/core|{{{2}}}}}}}<!-- -->{{#if:{{{3|}}}|{{{chain second|{{{chain|+}}}}}}{{key press/core|{{{3}}}}}}}<!-- -->{{#if:{{{4|}}}|{{{chain third|{{{chain|+}}}}}}{{key press/core|{{{4}}}}}}}<!-- -->{{#if:{{{5|}}}|{{{chain fourth|{{{chain|+}}}}}}{{key press/core|{{{5}}}}}}}<!-- -->{{#if:{{{6|}}}|{{{chain fifth|{{{chain|+}}}}}}{{key press/core|{{{6}}}}}}}<!-- -->{{#if:{{{7|}}}|{{{chain sixth|{{{chain|+}}}}}}{{key press/core|{{{7}}}}}}}<!-- -->{{#if:{{{8|}}}|{{{chain seventh|{{{chain|+}}}}}}{{key press/core|{{{8}}}}}}}<!-- -->{{#if:{{{9|}}}|{{{chain eighth|{{{chain|+}}}}}}{{key press/core|{{{9}}}}}}}<!-- -->{{#if:{{{10|}}}|{{{chain ninth|{{{chain|+}}}}}}{{key press/core|{{{10}}}}}}}<!-- -->{{#if:{{{11|}}}|[[Category:Wikipedia keypress template parameter needs fixing]]}}<noinclude> {{documentation}} <!-- add category and language links to the /doc sub-page, not here --> </noinclude> ec13a6d48bf0d5a168557926c766b9bc533d0506 10 45 11525 11524 2016-06-19T20:38:27Z Wottem 21 2 Versionen importiert wikitext text/x-wiki <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; {{border-radius|0.2em}} {{box-shadow|0.1em|0.2em|0.2em|#ddd}} background-color: #f9f9f9; {{linear-gradient|top|#eee, #f9f9f9, #eee}} padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">{{#switch:{{lc:{{{1}}}}} | caps lock = {{Unicode|⇪}} Caps Lock | [[caps lock]] = {{Unicode|⇪}} [[Caps Lock]] | shift = {{Unicode|⇧}} Shift | [[shift key|shift]] = {{Unicode|⇧}} [[Shift key|Shift]] | enter = {{Unicode|↵}} Enter | [[enter key|enter]] = {{Unicode|↵}} [[Enter key|Enter]] | cmd = {{Unicode|⌘}} Cmd | [[cmd key|cmd]] | [[command key|cmd]] = {{Unicode|⌘}} [[Command key|Cmd]] | command = {{Unicode|⌘}} Command | [[cmd key|command]] | [[command key|command]] = {{Unicode|⌘}} [[Command key|Command]] | opt = {{Unicode|⌥}} Opt | [[opt key|opt]] | [[option key|opt]] = {{Unicode|⌥}} [[Option key|Opt]] | option = {{Unicode|⌥}} Option | [[option key]] | [[opt key|option]] | [[option key|option]] = {{Unicode|⌥}} [[Option key|Option]] | tab = Tab {{Unicode|↹}} | [[tab key|tab]] = [[Tab key|Tab]] {{Unicode|↹}} | backspace = ← Backspace | [[backspace]] = ← [[Backspace]] | win = {{Unicode|⊞}} Win | [[win key|win]] | [[windows key|win]] = {{Unicode|⊞}} [[Windows key|Win]] | menu = {{Unicode|≣}} Menu | [[menu key|menu]] = {{Unicode|≣}} [[Menu key|Menu]] | up = ↑ | [[arrow keys|up]] = [[Arrow keys|↑]] | down = ↓ | [[arrow keys|down]] = [[Arrow keys|↓]] | left = ← | [[arrow keys|left]] = [[Arrow keys|←]] | right = → | [[arrow keys|right]] = [[Arrow keys|→]] | * | asterisk = <nowiki>*</nowiki> | # | hash = <nowiki>#</nowiki> | [[#]] = [[Number sign|#]] | : | colon = <nowiki>:</nowiki> | [[:]] = [[Colon (punctuation)|:]] | pipe = <nowiki>|</nowiki> | [[|]] = [[Pipe symbol|<nowiki>|</nowiki>]] | ; | semicolon = <nowiki>;</nowiki> | [[;]] = [[Semi-colon|<nowiki>;</nowiki>]] | equals = <nowiki>=</nowiki> <!-- Left & right analog sticks --> | l-up | l up = L↑ | l-down | l down = L↓ | l-left | l left = L← | l-right | l right = L→ | l-ne | l ne = L↗ | l-se | l se = L↘ | l-nw | l nw = L↖ | l-sw | l sw = L↙ | r-up | r up = R↑ | r-down | r down = R↓ | r-left | r left = R← | r-right | r right = R→ | r-ne | r ne = R↗ | r-se | r se = R↘ | r-nw | r nw = R↖ | r-sw | r sw = R↙ <!-- PlayStation --> | ps x | ex = {{unicode|×}} | ps c | circle = {{unicode|○}} | ps s | square = {{unicode|□}} | ps t | triangle = {{unicode|△}} <!-- Nintendo 64 & GameCube --> | c-up | c up = C↑ | c-down | c down = C↓ | c-left | c left = C← | c-right | c right = C→ | c-ne | c ne = C↗ | c-se | c se = C↘ | c-nw | c nw = C↖ | c-sw | c sw = C↙ <!-- default --> | #default = {{{1}}} }}</kbd><noinclude> {{documentation}} <!-- Add categories and interwikis links to the /doc subpage, not here! --> </noinclude> 03657747b458c57b74fdc4e0925eb5776ac2eccf 10 46 11528 11527 2016-06-19T20:38:27Z Wottem 21 2 Versionen importiert wikitext text/x-wiki <includeonly>background-image: -moz-linear-gradient({{{1|}}}, {{{2|}}}); background-image: -o-linear-gradient({{{1|}}}, {{{2|}}}); background-image: -webkit-linear-gradient({{{1|}}}, {{{2|}}}); background-image: linear-gradient({{Linear-gradient/legacy|{{{1|}}}}}, {{{2|}}});</includeonly><noinclude> <!-- ADD CATEGORIES AND INTERWIKIS TO THE /doc PAGE, NOT HERE, THANKS --> {{documentation}} </noinclude> c8f4766d7ac860c26118a121480308ed58699a4a 10 47 11531 11530 2016-06-19T20:38:27Z Wottem 21 2 Versionen importiert wikitext text/x-wiki {{#switch: {{{1|}}} | top = to bottom | bottom = to top | left = to right | right = to left | top left | left top = to bottom right | top right | right top = to bottom left | bottom left | left bottom = to top right | bottom right | right bottom = to top left | #default = {{{1}}} }} 519d0c5417b418a0e87b1360cd516f177ddc6ea4 10 48 11560 11559 2016-06-19T20:38:29Z Wottem 21 28 Versionen importiert wikitext text/x-wiki <includeonly><div class="toccolours mw-collapsible {{#ifeq: {{{expand|}}}|yes||mw-collapsed}}" style="width:{{{width|600px}}}; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius: 10px; border: solid 2px #87CEEB; font-size: 70%; background-color: #FBFDFD"> '''navigation rapide vers...''' <div class="mw-collapsible-content"> <table> {{#if: {{{1|}}} | {{Navigation rapide/Sub1 | level={{{1}}} | link1={{{2}}} | link2={{{3}}} }} }} {{#if: {{{4|}}} | {{Navigation rapide/Sub1 | level={{{4}}} | link1={{{5}}} | link2={{{6}}} }} }} {{#if: {{{7|}}} | {{Navigation rapide/Sub1 | level={{{7}}} | link1={{{8}}} | link2={{{9}}} }} }} {{#if: {{{10|}}} | {{Navigation rapide/Sub1 | level={{{10}}} | link1={{{11}}} | link2={{{12}}} }} }} {{#if: {{{13|}}} | {{Navigation rapide/Sub1 | level={{{13}}} | link1={{{14}}} | link2={{{15}}} }} }} {{#if: {{{16|}}} | {{Navigation rapide/Sub1 | level={{{16}}} | link1={{{17}}} | link2={{{18}}} }} }} {{#if: {{{19|}}} | {{Navigation rapide/Sub1 | level={{{19}}} | link1={{{20}}} | link2={{{21}}} }} }} {{#if: {{{22|}}} | {{Navigation rapide/Sub1 | level={{{22}}} | link1={{{23}}} | link2={{{24}}} }} }} {{#if: {{{25|}}} | {{Navigation rapide/Sub1 | level={{{25}}} | link1={{{26}}} | link2={{{27}}} }} }} {{#if: {{{28|}}} | {{Navigation rapide/Sub1 | level={{{28}}} | link1={{{29}}} | link2={{{30}}} }} }} {{#if: {{{31|}}} | {{Navigation rapide/Sub1 | level={{{31}}} | link1={{{32}}} | link2={{{33}}} }} }} {{#if: {{{34|}}} | {{Navigation rapide/Sub1 | level={{{34}}} | link1={{{35}}} | link2={{{36}}} }} }} {{#if: {{{37|}}} | {{Navigation rapide/Sub1 | level={{{37}}} | link1={{{38}}} | link2={{{39}}} }} }} </table> </div></div> {{Clear}} </includeonly> <noinclude>{{Documentation}}</noinclude> 586a68c9f556a795f36996271926924ae65037b0 10 49 11583 11582 2016-06-19T20:38:31Z Wottem 21 22 Versionen importiert wikitext text/x-wiki {{Navigation rapide | expand={{{expand|}}} |1| Accueil Edition | Edition de la Carte |2| Règles d'édition | [[Dernières informations et directives]] ● [[Principales directives d'édition]] |2| Waze Map Editor (WME) | [[Protections de la carte]] ● |2| Classification France | |2| Les limitations de vitesse | |2| Nommage | [[Numéros de rue]] ● [[Propagation du nommage des segments]] |2| Connectivité | [[Connectivité inversée]] |1| Les articles ci-dessous n'ont pas encore été révisés | {{PAGENAME}} |2| Edition Premiers pas | [[Bonnes pratiques d'édition de carte | Bonnes pratiques]] ● [[Edition base | Bien débuter ]] ● [[Edition/Ponts_Tunnels | Ponts et Tunnels]] |2| Connectivité | [[Guide des intersections | Intersections]] ● [[Tout sur les ronds-points | Rond-points]] ● [[Soft et hard turns]] |2| Requêtes et Problèmes | [[Les Erreurs de carte (UR) dans l'éditeur | Update Requests]] ● [[Les Problèmes de carte (MP) dans l'éditeur | Map Problems]] |2| Lieux | [[Normalisation des POI | Normalisation]] ● [[Lieux/Zones_Activite | Zones d'Activités]] ● [[Lieux/Parkings | Parking]] ● [[Stations essence]] ● [[Tout sur les radars | Radars]] ● [[Mise à jour de Lieux (modération) | Place Update]] |2| Fermetures | [[Comment gérer les fermetures de routes | Comment les gérer]] ● [[Les fermetures programmées | Fermetures programmée]] |2| Itinéraires et Navigation | [[Manière dont Waze calcule les itinéraires | Calcul d'itinéraire]] ● [[Comment Waze détermine les instructions de guidage ? | Instructions de navigation]] }} a4f1d46e1217fc52862e8914975a2da56d4c11eb 10 50 11622 11621 2016-06-19T20:38:33Z Wottem 21 38 Versionen importiert wikitext text/x-wiki <includeonly> <tr> {{#ifeq: {{{level|}}} | 1 | <td style="width:570px; background-color: #208FBF; text-align: center; padding:0px 10px 0px 10px; -moz-border-radius: 8px; -webkit-border-radius: 8px; border-radius: 8px;" colspan=2>[[ {{#if: {{{link2}}} | {{{link2|}}} | {{{link1|}}} }} | <span style="color:white">'''{{#titleparts: {{{link1|}}} | | -1}}'''</span> ]]</td> | {{#ifeq: {{{level|}}} | 2 | {{#if: {{{link1|}}} | <td style="width:150px; background-color: skyblue; color:black; padding:0px 10px 0px 10px; -moz-border-radius: 8px; -webkit-border-radius: 8px; border-radius: 8px;">{{#ifexist: {{{link1}}} | [[ {{{link1}}} | {{#ifeq: {{#titleparts: {{{link1|}}} | | -1}} | FR | '''{{#titleparts: {{{link1|}}} | -1}}''' | '''{{#titleparts: {{{link1|}}} | | -1}}''' }} ]] | {{{link1}}} }}</td> | <td style="width:150px;"></td> }} {{#if: {{{link2|}}} | <td style="width:420px; background-color: #CCEAF7; color:black; padding:0px 10px 0px 10px; -moz-border-radius: 8px; -webkit-border-radius: 8px; border-radius: 8px;">{{{link2|}}}</td> }} }} }} </tr> </includeonly> de38ddc21533f81a4aa18106da24b4743c6a8c06 10 51 11624 11623 2016-06-19T20:38:34Z Wottem 21 1 Version importiert wikitext text/x-wiki {{#expr: +{{#if:{{{1|}}}|1|0}} +{{#if:{{{2|}}}|1|0}} +{{#if:{{{3|}}}|1|0}} +{{#if:{{{4|}}}|1|0}} +{{#if:{{{5|}}}|1|0}} +{{#if:{{{6|}}}|1|0}} +{{#if:{{{7|}}}|1|0}} +{{#if:{{{8|}}}|1|0}} +{{#if:{{{9|}}}|1|0}} +{{#if:{{{10|}}}|1|0}} +{{#if:{{{11|}}}|1|0}} +{{#if:{{{12|}}}|1|0}} +{{#if:{{{13|}}}|1|0}} +{{#if:{{{14|}}}|1|0}} +{{#if:{{{15|}}}|1|0}} +{{#if:{{{16|}}}|1|0}} +{{#if:{{{17|}}}|1|0}} +{{#if:{{{18|}}}|1|0}} +{{#if:{{{19|}}}|1|0}} +{{#if:{{{20|}}}|1|0}} }}<noinclude>{{Documentation}}</noinclude> 2007a2ee8ed85b3910b243bed83ee6fb93073c3c 10 52 11631 11630 2016-06-19T20:38:34Z Wottem 21 6 Versionen importiert wikitext text/x-wiki <span style="color:#FF0000">{{{1|}}}</span><noinclude>{{doc}}</noinclude> f75c559fc96e089c2981bc3ffd651fd873827dca 10 53 11665 11664 2016-06-19T20:38:36Z Wottem 21 33 Versionen importiert wikitext text/x-wiki <includeonly>{{#if:{{{first|}}}||{{#ifeq:{{#expr:{{#if:{{{rounding|}}}|0|1}} or {{#if:{{{gap|}}}|1|0}}}}|1|<td class="tab" style="width: {{{gap|2%}}}; border-bottom: {{#if:{{{border|}}}|{{{border}}}|solid 2px #87CEEB}}">&nbsp;</td>}}}}<td class="tab" style="text-align: {{#if:{{{tab align|}}}|{{{tab align}}}|center}}; {{#if:{{{rounding|}}}|-moz-border-radius: {{#if:{{{asym|}}}|{{#expr:{{{rounding}}}*{{{asym}}}}}|{{{rounding}}}}}px {{{rounding}}}px 0 0; -webkit-border-radius: {{#if:{{{asym|}}}|{{#expr:{{{rounding}}}*{{{asym}}}}}|{{{rounding}}}}}px {{{rounding}}}px 0 0; border-radius: {{#if:{{{asym|}}}|{{#expr:{{{rounding}}}*{{{asym}}}}}|{{{rounding}}}}}px {{{rounding}}}px 0 0;}} padding:0.3em; border: {{#if:{{{border|}}}|{{{border}}}|solid 2px #87CEEB}}; font-size: {{{font size|100%}}}; {{#ifeq:{{#expr:{{#ifeq:{{{selected}}}|{{{Tab}}}|1|0}} or {{#ifeq:{{anchorencode:{{FULLPAGENAME}}}}|{{anchorencode:{{{URL}}}}}|1|0}}}}|1|background-color: {{#if:{{{frame background|}}}|{{{frame background}}}|transparent}}; border-bottom: none; |background-color: {{#if:{{{tab background|}}}|{{{tab background}}}|#D3D3D3}}; }}" width="{{#expr:(100/{{{tab count|{{ParamCount|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|{{{5}}}|{{{6}}}|{{{7}}}|{{{8}}}|{{{9}}}|{{{10}}}}}}}})-2}}%">{{#if:{{{Image|}}}|[[File:{{{Image}}}|{{#if:{{{image size|}}}|{{{image size}}}|25px}}|{{{Tab}}}|link={{{URL}}}]]&nbsp;|}}[[{{{URL}}}|{{{Tab}}}]]</td></includeonly><noinclude>{{Documentation}}</noinclude> 2aad27aab6373e67cb09cedd66f85ae3eca17dfd 10 54 11706 11705 2016-06-19T20:38:39Z Wottem 21 40 Versionen importiert wikitext text/x-wiki <includeonly><!-- --><table width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" style="background-color: transparent;"><!-- --><tr><!-- -->{{#if:{{{Tab-1|}}}|{{Tab|URL={{{URL-1}}}|Tab={{{Tab-1}}}|Image={{{Image-1|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-1|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-1|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}|first=1}}}}<!-- -->{{#if:{{{Tab-2|}}}|{{Tab|URL={{{URL-2}}}|Tab={{{Tab-2}}}|Image={{{Image-2|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-2|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-2|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- -->{{#if:{{{Tab-3|}}}|{{Tab|URL={{{URL-3}}}|Tab={{{Tab-3}}}|Image={{{Image-3|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-3|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-3|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- -->{{#if:{{{Tab-4|}}}|{{Tab|URL={{{URL-4}}}|Tab={{{Tab-4}}}|Image={{{Image-4|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-4|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-4|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- -->{{#if:{{{Tab-5|}}}|{{Tab|URL={{{URL-5}}}|Tab={{{Tab-5}}}|Image={{{Image-5|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-5|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-5|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- -->{{#if:{{{Tab-6|}}}|{{Tab|URL={{{URL-6}}}|Tab={{{Tab-6}}}|Image={{{Image-6|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-6|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-6|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- -->{{#if:{{{Tab-7|}}}|{{Tab|URL={{{URL-7}}}|Tab={{{Tab-7}}}|Image={{{Image-7|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-7|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-7|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- -->{{#if:{{{Tab-8|}}}|{{Tab|URL={{{URL-8}}}|Tab={{{Tab-8}}}|Image={{{Image-8|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-8|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-8|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- -->{{#if:{{{Tab-9|}}}|{{Tab|URL={{{URL-9}}}|Tab={{{Tab-9}}}|Image={{{Image-9|}}}|tab count={{ParamCount|{{{Tab-1|}}}|{{{Tab-2|}}}|{{{Tab-3|}}}|{{{Tab-4|}}}|{{{Tab-5|}}}|{{{Tab-6|}}}|{{{Tab-7|}}}|{{{Tab-8|}}}|{{{Tab-9|}}}}}|rounding={{{rounding|}}}|asym={{{asym|}}}|border={{{border|}}}|tab background={{{tab background-9|{{{tab background|}}}}}}|frame background={{{frame background|}}}|tab align={{{tab align-9|{{{tab align|}}}}}}|gap={{{gap|}}}|font size={{{font size|}}}|image size={{{image size|}}}|selected={{{selected|}}}}}}}<!-- --></tr><!-- --></table><!-- -->{{#ifeq:{{{frame}}}|No||<div style="border:{{{border|solid 2px #87CEEB}}}; padding: .5em 1em 1em 1em; border-top: none; background-color:{{{frame background|transparent}}}; color:#000;zoom: 1"><!-- --><div style="padding:1ex; ">}}<!-- --></includeonly><noinclude>{{Documentation}}</noinclude> 678ea4f3b737e4f99a69d7b432db13243737f6db 10 55 11709 11708 2016-06-19T20:38:39Z Wottem 21 2 Versionen importiert wikitext text/x-wiki <span class="Unicode">{{{1}}}</span><noinclude> {{documentation}} </noinclude> ff038df4400b7f63b01ab8dbd458bcb16437c79c 2 56 11715 11714 2016-06-19T20:38:40Z Wottem 21 5 Versionen importiert wikitext text/x-wiki Cette page contient les différentes notifications que j'utilise sur le wiki === Message ID 001 - Warning Général sur la refonte du wiki === <onlyinclude>{{#ifeq:{{{MsgID|001}}}|001| <!------------------------ MESSAGE 001 ------------------------------------------------------> {{mbox | type=caution | text=Sauf mention contraire, tous les articles sous l'onglet '''Edition''' sont en cours de révision. Ces articles sont donc susceptibles de contenir des liens qui mènent vers des pages obsolètes, vers des pages en anglais ou vers des pages supprimées.}} <!------------------------ FIN DU MESSAGE 001 -----------------------------------------------> }}</onlyinclude> === Message ID 002 - Page révisée et publiée === <onlyinclude>{{#ifeq:{{{MsgID|002}}}|002| <!------------------------ MESSAGE 002 ------------------------------------------------------> {{mbox | type=notice | text=Cet article a été révisé et validé dans le cadre du projet de mise à jour du Wiki Français. Les informations ci-dessous sont donc d'actualité, parfaitement valides et prêtes à être appliquées.}} <!------------------------ FIN DU MESSAGE 002 -----------------------------------------------> }}</onlyinclude> === Message ID 003 - Page Obsolète === <onlyinclude>{{#ifeq:{{{MsgID|003}}}|003| <!------------------------ MESSAGE 003 ------------------------------------------------------> {{mbox | type=critical | textstyle = color: red; | text=Une partie importante des informations contenu dans cette page sont obsolètes et en cours de mise à jour. Avant d'appliquer ce qui est écrit ci-dessous, il peut être utile de le vérifier sur le [[Forum de discussion]]}} <!------------------------ FIN DU MESSAGE 003 -----------------------------------------------> }}</onlyinclude> === Message ID 004 - Manual Waze sur Help Center === <onlyinclude>{{#ifeq:{{{MsgID|004}}}|004| <!------------------------ MESSAGE 004 ------------------------------------------------------> {{mbox | type=move | text=Les informations relatives à l'application mobile Waze sont désormais hébergées sur le site web [http://support.google.com/waze Waze Help Center].}} <!------------------------ FIN DU MESSAGE 004 -----------------------------------------------> }}</onlyinclude> cb8337860e046db1744d95dec0ef5f95a406a6b3 10 57 11721 11720 2016-06-19T20:38:40Z Wottem 21 5 Versionen importiert wikitext text/x-wiki {{#ifeq:{{{small|}}}|yes | {{mbox/core | small = yes | type = {{{type|}}} | image = {{#if:{{{smallimage|}}}| {{{smallimage}}} | {{{image|}}} }} | imageright = {{#if:{{{smallimageright|}}} | {{{smallimageright}}} | {{{imageright|}}} }} | class = {{{class|}}} | style = {{{style|}}} | textstyle = {{{textstyle|}}} | text = {{#if:{{{smalltext|}}}| {{{smalltext}}} | {{{text}}} }} }} | {{mbox/core | type = {{{type|}}} | image = {{{image|}}} | imageright = {{{imageright|}}} | class = {{{class|}}} | style = {{{style|}}} | textstyle = {{{textstyle|}}} | text = {{{text}}} }} }}<noinclude>{{documentation}}<!-- Add categories and interwikis to the /doc subpage, not here! --></noinclude> a821883ba56ac16c59c28518975bf032b6e2c478 10 58 11748 11747 2016-06-19T20:38:43Z Wottem 21 26 Versionen importiert wikitext text/x-wiki <table style=" border: 1px solid rgb(170, 170, 170); margin: 4px 5%; border-collapse: collapse; background: none repeat scroll 0% 0% rgb(249, 249, 249); {{{style|}}}"> <tr> {{#switch:{{{image|}}} | none = <td class="mbox-empty-cell"></td> <!-- No image. Cell with some width or padding necessary for text cell to have 100% width. --> | #default = <td style=" border: medium none; padding: 2px 0px 2px 0.9em; text-align: center; ">{{ #switch:{{{small|}}} | left = <!-- Don't use the DIV --> | #default = <div style="width: {{{imagewidth||52px}}};"> }} {{#if: {{{image|}}} | {{{image}}} | [[File:{{#if: {{{filename|}}} | {{{filename}}} | {{#switch:{{{type|}}} | critical = Mbox warning.png | warning = mbox warning yellow.png | important = Mbox important.png | caution = Mbox caution.png | speculation = Mbox speculation.png | move = Mbox move.png | protection = Mbox protection.png | license = Mbox license.png | construction = Mbox construction yellow.png | neweditor = Mbox new editor.png | mail = Mbox mail.png | forum = Gnome-system-users.svg.png | cleanup = Edit-clear.png | wiki = wikitext.png | notice <!-- notice = default --> | #default = Mbox information.png }} }} | {{#switch:{{{small|}}} | left = 20x20px | #default = 40x40px }} |link=|alt=]] }}{{#switch:{{{small|}}} | left = <!-- Don't use the /DIV --> | #default = </div> }}</td> }} <td style=" width: 100%; border: medium none; padding: 0.25em 0.9em; {{{textstyle|}}}"> {{{text}}} </td> {{#if:{{{imageright|}}} | {{#ifeq:{{{imageright|}}}|none | <!-- No image. --> | <td class="mbox-imageright">{{#switch:{{{small|}}} | left = {{{imageright}}} | #default = <div style="width: {{{imagerightwidth|52px}}};"> {{{imageright}}} </div> }}</td> }} }} </tr> </table><noinclude> {{Documentation|content=This subtemplate supports the default values of {{tl|Mbox}}. It should not be altered without review from a Wiki Expert. Contact one through the [http://www.waze.com/forum/viewforum.php?f=276 Wiki Updates and Discussion forum.]}} <!-- This category is only for the template itself --> [[Category:Template:Mbox]] </noinclude> b82054418fd6c64d000e0b5b5e581d9a5f09f3a3 10 59 11752 11751 2016-06-19T20:38:43Z Wottem 21 3 Versionen importiert wikitext text/x-wiki <div style="border:solid 2px #CC0000; padding: .5em 1em 1em 1em; background-color:#FFE7E1; border-radius: 5px; color:#000;zoom: 1"><div style="float:left;padding-right:10px">[[File:Warning.png|50px]]</div>{{Resize|75%|{{Red|Cette section contient des '''directives qui sont dépassées''' et ne doit plus être appliquée telle que rédigée. Rapprochez-vous des Country Managers en attendant la mise à jour du wiki}}}}<br /> {{{1|}}}</div> 2ae669913de03244667fd2104b9b4ef6fde593cb 10 60 11755 11754 2016-06-19T20:38:44Z Wottem 21 2 Versionen importiert wikitext text/x-wiki {{#if:{{{2|}}} |<span style="font-size:{{{1|}}};">{{{2|}}}</span> |<span style="font-size:90%;">{{{1}}}</span> }}<noinclude> {{documentation}} <!--PLEASE ADD CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS--> </noinclude> c8427f2cd651103e89fd3d59c8447aa726de35b6 0 61 11758 11757 2016-06-19T20:38:45Z Wottem 21 2 Versionen importiert wikitext text/x-wiki {{France Tabs|Communauté}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> {{Collapsible section top}} == Classement général et Rangs == Ces points accumulés vous positionnent dans un classement quotidiennement par rapport aux autres wazers. Il existe un classement global qui regroupent tous les pays et zones desservies par le serveur Waze auquel nous sommes rattachés et, plus localement, il existe aussi un classement Français qui vous positionne parmi les autres Wazers en France. {{Collapsible section content}} Le calcul de vos points ainsi que la mise à jour du classement est effectuée en tâche de fond, généralement durant la nuit en France. Les points sont mis à jour en premier, utilisateur par utilisateur. Ensuite le système calcul le nouveau classement. Vous pouvez donc observer une mise à jour de vos points mais pas encore celui de votre classement. Il suffit de patienter quelques heures. Enfin dans certains cas, suite à un charge de traitement importante des serveurs Waze, il est possible que ces calculs de points et de classement soient reportés d'un ou plusieurs jours. Si vous constatez pendant plus de 48h un soucis sur la mise à jour de vos points, pensez à consulter le [http://status.waze.com rapport d'état de Waze] qui peut stipuler ce type de retard. Votre position dans ce classement vous permet d'atteindre des Rangs qui, par exemple, vous donnent accès à un look légèrement différent de votre avatar (en lui ajoutant une épée, un bouclier ou une couronne). <table border="1" align="center" style="text-align:left;"> <tr> <td style="text-align:center;">[[Image:Waze level Baby.png|40px]]'''Bébé Waze'''</td> <td>Vous venez d'arriver dans l'univers de Waze. Vous êtes un bébé wazer mais pas pour très longtemps. Conduisez avec Waze sur 160km pour passer au Rang suivant</td> </tr><tr> <td style="text-align:center;">[[Image:Waze level Waze.png|40px]]'''Adulte Waze'''</td> <td>Vous avez grandi et vous pouvez maintenant modifier votre humeur. Le prochain niveau sera atteint en accumulant les points</td> </tr><tr> <td style="text-align:center;">[[Image:Waze level Shield.png|40px]]'''Guerrier Waze'''</td> <td>Contemplez votre bouclier ! Vous êtes désormais classé parmi les 10% des meilleurs wazers de France</td> </tr><tr> <td style="text-align:center;">[[Image:Waze level Sword.png|40px]]'''Chevalier Waze'''</td> <td>Voici votre épée ! Vous êtes désormais classé parmi les 4% des meilleurs wazers de France</td> </tr><tr> <td style="text-align:center;">[[Image:Waze level King.png|40px]]'''Prince Waze'''</td> <td>Vous y êtes arrivé ! Vous êtes désormais classé parmi les 1% des meilleurs wazers de France</td> </tr> </table> {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> ccfb61cb0de888a39d4eaf3a188285f8e1fa0f0f 0 62 11767 11766 2016-06-19T20:38:47Z Wottem 21 8 Versionen importiert wikitext text/x-wiki {{France Tabs|Communauté}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> {{Collapsible section top}} == {{@|Comment sont attribués les points ?}} == Les points proviennent de 2 sources. D'une part vous recevez un certain nombre de points, de manière régulière, pour chaque activité listée dans le tableau ci-dessous. D'autre part vous pourrez également collecter, de manière exceptionnelle, des points supplémentaires en obtenant des '''Bonus''' liés à certaines actions ou étapes de votre activité de Wazer ou d'éditeur de la Carte (voir plus bas la section sur les Bonus) {{Collapsible section content}} === Attribution de points === <table class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"> <tr> <th>Activité</th><th>Points</th><th>Déclencheur</th> </tr><tr> <td>Signaler un événement sur la route¹</td><td>6</td><td>par signalement </tr><tr> <td>Mettre à jour des tarifs de carburants</td><td>8</td><td>par mise à jour </tr><tr> <td>Commenter des signalements</td><td>3</td><td>par commentaire </tr><tr> <td>Editer la Carte²</td><td>3</td><td>par édition³ </tr><tr> <td>Photographier un Lieu</td><td>6</td><td>par photo </tr><tr> <td>Mettre à jour un Lieu</td><td>3</td><td>par détail ajouté⁴ </tr><tr> <td>Résoudre une demande de mise à jour de la Carte</td><td>3</td><td>par demande résolue </tr><tr> <td>Ajouter des noms de rues</td><td>3</td><td>par nom ajouté⁵ </tr><tr> <td>Ajouter des numéros aux rues</td><td>1</td><td>par segment de route </tr><tr> <td>Poster des messages sur le Forum</td><td>2</td><td>tous les 3 posts </tr><tr> <td>Bonus sur la route</td><td>Valeur du bonus</td><td>par bonus mangé </tr><tr> <td>Conduire avec Waze ⁶</td><td>3,2</td><td>par km parcouru </tr><tr> <td>Manger des cookies ⁷</td><td>10</td><td>par km mangé </tr><tr> <td>Créer une nouvelle route (bulldozer)</td><td>40</td><td>par km créé </tr></table> ⁽¹⁾<small>les Pings, les Chit-chats et leur commentaires ne donnent pas de points</small> ⁽²⁾<small>L'édition de masse (sélection de plusieurs segments pour le mettre à jour) considère chaque segment comme modifié séparément. En revanche, l'ensemble des modifications apportées à la géométrie d'un segment est comptabilisé comme une seule édition par segment modifié. Notez qu'il ne faut pas confondre le compteur de changement non-sauvegardés qui s'affiche sur l'icône de sauvegarde dans Waze Map Editor et le nombre de points collectés. Voir le paragraphe plus bas pour davantage de précisions</small> ⁽³⁾<small>Il existe, pour le moment, un bonus additionnel de points pour les éditeurs, distribué sous la forme d'un bonus routier qui s'affiche toutes les 3000 éditions sur la Carte et qui rapporte 300 points</small> ⁽⁴⁾<small>Ajout d'une catégorie, mise à jour de la position du Lieu, préciser les horaires d'ouverture, indiquer les services, donner une description, un numéro de téléphone ou l'adresse d'un site web</small> ⁽⁵⁾<small>Uniquement si aucun nom n'a jamais encore été donné à ce segment</small> ⁽⁶⁾<small>Qu'un itinéraire soit programmé ou non</small> ⁽⁷⁾<small>Les routes récemment cartographiées ont besoin d'être confirmées physiquement sur le terrain, ce que vous pouvez faire en roulant le premier sur cet axe. Les axes ainsi créés sont représentés avec les petits points dessus (qu'on appelle des cookies) que vous dévorez en roulant dessus.</small> === Qu'est-ce qu'une édition de la Carte === Quand vous cartographiez dans Waze Map Editor, les points vous sont attribués en fonction du nombre d'objets (segments, noeuds, Lieux, etc.) modifiés. Si vous avez sélectionné plusieurs objets et que vous les modifiez tous ensemble d'un coup, vous obtiendrez des points pour chacun des segments compris dans la sélection. Cependant vous n'obtiendrez pas davantage de points si vous modifiez plusieurs propriétés d'un même segment. Il ne faut pas confondre le compteur de modifications (qui s'affiche sur l'icône de sauvegarde dans l'interface de WME et qui indique le nombre de changements "annulables" que vous avez réalisés) et le nombre d'éditions comptabilisés au moment de la sauvegarde et génératrices de points. Par exemple, si vous sélectionnez 10 segments dont vous modifiez le nom de la ville, une fois que vous cliquez sur "Appliquer", le compteur de changement augmente de 1. Du point de vue de Waze Map Editor, vous venez de faire un seule action annulable, donc 1 seul changement. Par contre, Waze comptabilisera 10 éditions pour le calcul de points car vous avez modifié 10 objets différents. Maintenant si vous sélectionnez 1 seul segment et que vous corrigez la position de ses noeuds de géométrie dans un virage, chaque fois que vous déplacer un noeud de géométrie, c'est une action annulable isolément et cela incrémente de 1 le compteur de changement sur l'icône de sauvegarde. Et pourtant Waze ne comptabilisera qu'une seule édition pour le calcul de points, car vous n'avez modifié qu'un seul objet. Enfin, si vous mettez à jour un long segment, en lui donnant un nouveau nom de rue, en changeant la ville, son type de route, son sens de circulation, le niveau de verrouillage et son élévation, puis que vous ajustez la position de plus de 100 noeuds de géométrie, le compteur de sauvegarde indiquera probablement 160 changements. Quand vous sauvegarderez, cela sera comptabilisé par Waze comme une seule édition pour ce segment. Autoriser ou Interdire des changements de directions compte pour 1 changement au niveau du noeud du changement de direction. Tous les changements de directions effectués sur ce noeud comptent pour une seule édition. L'édition répétée (même avec sauvegarde entre chaque modification) d'un même objet dans un même période de 24 heures ne génère de points que pour une seule édition dans cette période de 24h. Enfin le système ne vous attribuera jamais plus de 150 points par sauvegarde. Ainsi, si vous avez un grand nombre de modifications (toutes susceptibles chacune de générer des points) en attente de sauvegarde, la sauvegarde prendra en compte toutes vos modifications mais le cumul des points attribués n’excédera pas 150 points. === Bonus exceptionnels === Il existe une autre façon de gagner des points: L'obtention de Bonus exceptionnels pour l'atteinte de critères présentés plus bas. Lorsque vous aurez rempli les critères en question, votre application mobile fera apparaître sur votre trajet un bonbon coloré stipulant un nombre de points. Lorsque vous "roulerez" dessus, vous obtiendrez un message sur votre application vous indiquant que vous venez de manger un "bonbon" qui contient "…"points. <table class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1"> <tr> <th scope="col" width="300">Tâche</th> <th scope="col" width="40">Points</th> <th scope="col" width="350">Notes</th> </tr><tr> <td>Vos 16 premiers kilomètres</td> <td>25</td> <td></td> </tr><tr> <td>Votre premier signalement</td> <td>25</td> <td></td> </tr><tr> <td>Votre premier signalement en week-end</td> <td>30</td> <td></td> </tr><tr> <td>Votre premier signalement d'un problème de carte</td> <td>50</td> <td></td> </tr><tr> <td>Votre premier ami sur Waze</td> <td>200</td> <td>''Vous l'obtiendrez uniquement si Waze est connecté à Facebook et à la condition que votre ami soit aussi connecté à Waze et à Facebook.''</td> </tr><tr> <td>Votre première semaine où vous conduisez 2 jours</td> <td>100</td> <td>''une semaine commence le lundi et se finit le dimanche''</td> </tr><tr> <td>Votre première semaine où vous conduisez 3 jours</td> <td>200</td> <td>''une semaine commence le lundi et se finit le dimanche''</td> </tr><tr> <td>Votre première semaine où vous conduisez 4 jours</td> <td>300</td> <td>''une semaine commence le lundi et se finit le dimanche''</td> </tr><tr> <td>Votre première édition de Carte</td> <td>200</td> <td></td> </tr><tr> <td>Vous avez résolu vos 50 premiers problèmes de Carte</td> <td>500</td> <td></td> </tr><tr> <td>Vous êtes pour la première fois le meilleur Wazer dans votre pays</td> <td>500</td> <td>''Dans le classement hebdomadaire, du lundi au dimanche''</td> </tr><tr> <td>Vous conduisez pour la première fois au moins 800 km sur une semaine</td> <td>1000</td> <td>''une semaine commence le lundi et se finit le dimanche''</td> </tr><tr> <td>Vous avez pour la première fois 5 amis sur Waze</td> <td>2000</td> <td>''même remarque que sur le 1er ami, plus haut''</td> </tr><tr> <td>Vous avez réalisé 500 éditions sur la Carte</td> <td>750</td> <td>ce bonus est le seul qui peut s'obtenir plusieurs fois. il n’apparaît qu'après la publication des mises à jour de la Carte par les serveurs Waze</td> </tr> </table> Si vous pensez avoir accomplis l'un des critères ci-dessus, mais que vous n'obtenez pas le bonus associé, il suffit parfois d'attendre une semaine pour qu'il soit traité par le serveur et distribué sur votre application. En outre, certains critères se mesurent sur une semaine complète du Lundi 00h00 au Dimanche 23h59 et le calcul est remis à zéro le lundi. Donc, ce type de bonus ne sera octroyé que si vous remplissez le critère entre le Lundi et le Dimanche de la même semaine. Enfin, certains bonus ne peuvent pas être gagnés la même semaine que d'autres bonus et nécessitent un cycle Lundi-Dimanche séparé pour être activés. {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> 987b6edaba6144191d5ff7c17ab78852b47c6de2 0 63 11772 11771 2016-06-19T20:38:49Z Wottem 21 4 Versionen importiert wikitext text/x-wiki {{France Tabs|Communauté}} <onlyinclude>{{#ifeq:{{{transcludesection|CONTENT}}}|CONTENT| <!------------------------ DO NOT EDIT ABOVE THIS LINE--------------------------------------> {{Collapsible section top}} == {{@|Consulter ses points et son classement}} == Vous pouvez consulter à tout moment le nombre de points que vous avez gagné et votre classement au sein de la communauté en utilisant * soit votre [http://www.waze.com/dashboard Tableau de Bord] sur le site web de Waze * soit votre application mobile, en sélectionnant dans le Menu l'option "''Mon Waze''" puis "''Mon classement''". {{Collapsible section content}} Sur l'interface web, vous obtiendrez un tableau comme celui ci-dessous. Il vous permet de voir votre progression et votre activité en tant que conducteur ou en tant qu'éditeur au profit de la communauté. Chaque nuit, les systèmes de Waze calculent votre contribution de la journée et les points ainsi générés puis mettent à jour le tableau. Puis les systèmes déterminent votre classement au sein de la communauté. En général votre rang dans le classement est mis à jour à un rythme quotidien jusqu'à ce que vous atteignez un niveau très haut dans le classement. Toutefois, occasionnellement, les systèmes peuvent prendre quelques jours pour mettre à jour les points et le classement. Si la situation perdure, n'hésitez pas à consulter la [http://status.waze.com page de statut de Waze] qui peut indiquer qu'une maintenance particulière est en cours. [[Image:Dashboard_fr.png|600px|center]] Sur la gauche de la page, sous l'icône Waze et votre pseudo sur Waze, vous avez votre nombre total de points et votre classement à l'échelle mondiale. Dans la partie centrale, vous retrouvez les différentes activités de Waze qui contribuent à la communauté et sont donc génératrices de points : * '''Tous les signalements''' dénombre les signalements que vous avez faits en conduisant, quelle que soit la nature du signalement. * '''Kilomètres parcourus''' indique le nombre de kilomètres parcourus avec Waze allumé, contribuant ainsi à remonter vers la communauté des informations temps-réel sur la fluidité ou la congestion du trafic. * '''Kilomètres de route créés''' indique le nombre de kilomètres de route que vous avez créés avec l'application mobile, en parcourant en mode bulldozer un axe routier qui n'était pas encore cartographié. * '''Cookies mangés en mètres''' indique le nombre de mètres de routes récemment cartographiées et que vous avez confirmé en roulant le premier sur cet axe. Les axes ainsi créés sont représentés avec les petits points dessus (qu'on appelle des cookies) que vous dévorez en roulant dessus. * '''Mises à jour de la carte''' indique le nombre de mises à jour que vous avez réalisées, en tant qu'éditeur de la Carte, sur l'interface web d'édition (Waze Map Editor). * '''Demande de mises à jour résolues''' dénombre les Demandes de mises à jour (''Update Request'') que vous avez traitées, en tant qu'éditeur, dans l'interface web d'édition (Waze Map Editor). * '''Message sur le forum''' indique le nombre de messages que vous avez postés sur le [[Forum de discussion]] de Waze. {{Collapsible section bottom}} <!------------------------ DO NOT EDIT BELOW THIS LINE--------------------------------------> }}</onlyinclude> b0eed765caeff25a9bce1f79c6e32fa0b6e72471 10 64 11779 11778 2016-06-19T20:38:50Z Wottem 21 6 Versionen importiert wikitext text/x-wiki {{Navigation rapide | expand={{{expand|}}} |1| Accueil Communauté Waze | Communauté Waze |2| Forum de discussion | |2| Points et Classement | |2| Rôles et attributions | |2| Mentorat | [[Guide du Mentorat Formel]] |2| Partages documentaires | [[Avancement des zones]] ● [[France/Checklist]] }} 0574931be120f8d6bd4ca2190602769c38e260e5 10 65 11783 11782 2016-06-19T20:38:50Z Wottem 21 3 Versionen importiert wikitext text/x-wiki <includeonly><div style="-webkit-column-count: {{{2|2}}}; /* Chrome, Safari, Opera */ -moz-column-count: {{{2|2}}}; /* Firefox */ column-count: {{{2|2}}};">{{{1|{{red|Error: You must put the content of the columns as the second unnamed parameter}}}}}</div></includeonly><noinclude>{{doc}}</noinclude> c7b859ab224dba497a97d4f55dd67d8251425bd3 10 66 11872 11871 2016-06-19T20:39:27Z Wottem 21 88 Versionen importiert wikitext text/x-wiki <noinclude>{{mbox|type=wiki|text=When you update this list, please also purge {{tl|Countries}} by [http://wiki.waze.com/wiki/index.php?action=purge&forcelinkupdate&title=Template:Countries clicking here].}}</noinclude> <ul style="list-style:none;margin:0" class="CountriesList"> <li>[[Image:Sq.png]] [[Albania]] <li>[[Image:Ar.png]] [[Argentina]] <li>[[Image:Au.png]] [[Australia]] <li>[[Image:Oesterreich.png]] [[Österreich|Austria (Österreich)]] <li>[[Image:Be.png]] [[Belgium]] <li>[[Image:Bh.png]] [[BiH|Bosnia and Herzegovina]] <li>[[Image:Br.png]] [[Brasil]] <li>[[Image:Bg.png]] [[България|Bulgaria (България)]] <li>[[Image:Ca.png]] [[Canada]] <li>[[Image:Cl.png]] [[Chile]] <li>[[Image:Cn.png]] [[中国|China (中国)]] <li>[[Image:Co.png]] [[Colombia]] <li>[[Image:Cr.png]] [[Costa Rica]] <li>[[Image:Cy.png]] [[Cyprus]] <li>[[Image:Cz.png]] [[Czech]] <li>[[Image:Dk.png]] [[Denmark]] <li>[[Image:Ee.png]] [[Eesti|Estonia]] <li>[[Image:Fi.jpg]] [[Finland]] <li>[[Image:Fr.png]] [[France]] <li>[[Image:De.png]] [[Deutschland|Germany (Deutschland)]] <li>[[Image:Gr.png]] [[Greece|Greece (Ελλάδα)]] <li>[[Image:Hu.png]] [[Hungary|Hungary (Magyarország)]] <li>[[Image:Ic.png]] [[Iceland]] <li>[[Image:India1.jpg]] [[India]] <li>[[Image:In.png]] [[Indonesia]] <li>[[Image:Ie.png]] [[Ireland]] <li>[[Image:Il.png]] {{PlainLinks|http://www.waze.com/he/wiki/index.php?title&#61;%D7%A2%D7%9E%D7%95%D7%93_%D7%A8%D7%90%D7%A9%D7%99 ישראל (Israel)}} <li>[[Image:It.png]] [[Italy]] <li>[[image:Japan-flag.jpg||25px]] [[日本|Japan (日本)]] <li>[[Image:Kr.png|25px]] [[Korea|Korea (대한민국)]] <li>[[Image:Kv.png]] [[Kosovo]] <li>[[Image:Lv.png]] [[Latvija|Latvia (Latviešu)]] <li>[[Image:Lithuania_flag.png|25px]] [[Lietuviškai|Lietuva (Lietuviškai)]] <li>[[Image:Lux.gif]] [[Luxembourg|Luxembourg (Lëtzebuerg)]] <li>[[Image:My.jpg]] [[Malaysia]] <li>[[Image:Mx.gif|25px]] [[México]] <li>[[Image:Na.png|25px]] [[Namibia]] <li>[[Image:Nl.png]] [[Nederland]] <li>[[Image:Nz.png]] [[New Zealand|New&nbsp;Zealand]] <li>[[Image:Ni.png]] [[Nicaragua]] <li>[[Image:Norway_flag.png]] [[Norway]] <li>[[Image:PE.png]] [[Perú]] <li>[[Image:Pl.png]] [[Poland]] <li>[[Image:Pt.png]] [[Portugal]] <li>[[Image:Ro.png]] [[Romania]] <li>[[Image:Ru.png]] [[Russia]] <li>[[Image:SRb.png]] [[Serbia]] <li>[[Image:Sg.png]] [[Singapore]] <li>[[Image:Sk.png]] [[Slovakia]] <li>[[Image:SI.png]] [[Slovenia]] <li>[[Image:Za.png]] [[South Africa|South&nbsp;Africa]] <li>[[Image:Es.png]] [[España|Spain (España)]] <li>[[Image:Sr.png]] [[Suriname]] <li>[[Image:Se.png]] [[Sweden]] <li>[[Image:Swiss1.gif]] [[Switzerland]] <li>[[Image:Th.png]] [[Thailand]] <li>[[Image:Turkey.png]] [[Türkiye|Turkey (Türkiye)]] <li>[[Image:Ua.jpg]] [[Ukraine]] <li>[[Image:Gb.png]] [[United Kingdom|United&nbsp;Kingdom]] <li>[[Image:Us.png]] [[USA]] <li>[[Image:Vn.png]] [[Vietnam|Vietnam (Việt Nam)]] </ul><!-- --><noinclude>[[Category:Country list]]</noinclude> cfca5ec1f2b500bd87d5071a48c51f907f3a505a 10 67 11876 11875 2016-06-19T20:39:27Z Wottem 21 3 Versionen importiert wikitext text/x-wiki <span class="plainlinks">[{{{1|http://www.testpage.com Do not include <nowiki>[]</nowiki> and replace {{u|'''&#61;'''}} with {{u|'''&amp;#61;'''}}}}}]</span><noinclude>{{doc}}</noinclude> 13a21a5556a2d71e3b78f04d40191ca1820d85ed 10 68 11898 11897 2016-06-19T20:39:29Z Wottem 21 21 Versionen importiert wikitext text/x-wiki <includeonly><nowiki>{{</nowiki>{{#if:{{{subst|}}}|[[Help:Templates#Substitution|subst]]:}}{{#ifeq:{{NAMESPACE:{{{1|{{FULLPAGENAME}}}}}}}||<!-- this is intended to be either a page in the main namespace or in the template namespace -->{{#ifeq:{{{1|{{FULLPAGENAME}}}}}|:{{PAGENAME:{{{1|{{FULLPAGENAME}}}}}}}<!-- this is intended to be in the main namespace -->|<nowiki>:</nowiki>[[:{{{LANG|}}}{{{SISTER|}}}{{{1|{{PAGENAME}}}}}|{{PAGENAME:{{{1|{{FULLPAGENAME}}}}}}}]]<!-- this is intended to be in the template namespace -->|[[:{{{LANG|}}}{{{SISTER|}}}Template:{{{1|{{PAGENAME}}}}}|{{{1|{{PAGENAME}}}}}]]}}<!-- namespace was included -->|[[:{{{LANG|}}}{{{SISTER|}}}{{{1|{{FULLPAGENAME}}}}}|{{{1|{{FULLPAGENAME}}}}}]] }}<nowiki>}}</nowiki></includeonly><noinclude> {{Documentation}} </noinclude> e296e95825a8759121af34c43f76df8778a72f6b 0 1 11899 10142 2016-06-19T20:42:55Z Wottem 21 Wottem moved page [[Switzerland]] to [[Hauptseite]] wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Guide de l'édition en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sites in english</p> <div style="padding:5px"> * [[How to label and name roads (Switzerland)]] * [[How to label and name roads|More countries]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 06f010f334cad5b3409e686ab9087cb28d4f676a 11910 11899 2017-05-03T09:03:35Z Vince1612 23 French speaking Switzerland section changes wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Informations en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Guide de l'édition en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 3a51958439b74ce49e9e2008acac9e979fc8c500 11911 11910 2017-05-03T09:06:54Z Vince1612 23 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Informations en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Guide de l'édition en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] c3f0e681e49e87f885a920f6fbcef141bfb342ec 11913 11911 2017-05-03T09:14:47Z Vince1612 23 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Pour les francophones</p> <div style="padding:5px"> Veuillez suivre ce lien pour obtenir des [[Informations en français]]. </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Guide de l'édition en français</p> <div style="padding:5px"> * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] cf0abb93275da867d3e3e4596cf92d231bb98059 11919 11913 2017-05-03T14:22:04Z Vince1612 23 Removed old section wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Pour les francophones</p> <div style="padding:5px"> Veuillez suivre ce lien pour obtenir des [[Informations en français]]. </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 4108a6397ebc1f809a6b2827d0f6e53f38db9e92 0 69 11900 2016-06-19T20:42:56Z Wottem 21 Wottem moved page [[Switzerland]] to [[Hauptseite]] wikitext text/x-wiki #WEITERLEITUNG [[Hauptseite]] 1b0facd6723a506ecd54af6070cbbf0ad50cb384 0 12 11901 10748 2017-04-07T11:01:29Z BellHouse 29 /* Deutschland */ L6 für tom-cat-67 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1 (inaktiv)||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} 6f2bf8792a02ce24e554182e307b40f5c6a0f000 0 2 11902 10161 2017-04-08T20:36:35Z Popel22 24 wikitext text/x-wiki * [[Diskussionsforum]] * [[Der Waze Chat]] * [[Straßen Berichte]] * [[Facebook Verbindung]] [[Facebook]] * [http://www.waze.com/blog/ Waze Blog] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 4ffd80168e7b21c5ef507d8982a829b3867b0c5e 0 70 11903 2017-04-08T20:37:44Z Popel22 24 facebook link eingefügt wikitext text/x-wiki https://www.facebook.com/WazeSwitzerland/ 229de9fde6c7184b9cfea6aa5738ed0637458739 11904 11903 2017-04-08T20:38:43Z Popel22 24 link wieder grlöäscht wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 71 11905 2017-04-08T20:39:05Z Popel22 24 Die Seite wurde neu angelegt: «https://www.facebook.com/WazeSwitzerland/» wikitext text/x-wiki https://www.facebook.com/WazeSwitzerland/ 229de9fde6c7184b9cfea6aa5738ed0637458739 0 72 11906 2017-04-08T20:42:54Z Popel22 24 kopiert von germany wikitext text/x-wiki == Der Chat generell == Waze bietet die Möglichkeit an, miteinander zu kommunizieren in der Waze-App. Du kannst einen Wazer auf der Karte antippen und ihm eine Nachricht senden, oder in bereits bestehenden Chats auf der Karte oder im Hauptmenü Kommentare schreiben. Folgende Möglichkeiten gibt es: * Map-Chats * Mitteilungen * Piep-Funktion Map-Chats werden auf der Karte des Wazers und auch für alle anderen sichtbar angezeigt. Mitteilungen sind privat, sie werden nur dem betreffenden Wazer angezeigt. Mit der Piep-Funktion kannst Du einen Wazer anpiepen, er erhält eine akustische ond optische Anzeige. Pieps, private Mitteilungen und Map-Chats geben keine Punkte mehr in Waze, da der Missbrauch dieser Funktion zu Spam geführt hat. Gebrauche daher diese Funktion mit Bedacht! == Sei anständig! == Bei Gebrauch des Chats ist der Anstand zu wahren. Jeglicher Missbrauch oder Äußerungen wie Beleidigungen, Diffamierung und sonstige rechtlich verbotenen Aussagen sind strikt zu unterlassen! Falls dies festgestellt oder gemeldet wird, wird das Benutzer-Konto von Waze blockiert, abgesehen von weiteren rechtlichen Schritten! == Probleme == Wenn Du Opfer von oben genannten Aussagen wurdest, wende Dich per Mail an den Support. Nenne den Benutzernamen der betreffenden Person und beschreibe Dein Problem. Bedenke, der Alias-Name, der in der Anwendung angezeigt wird, ist nicht immer der reale Benutzername. Waze hat jedoch die Möglichkeit, diesen zu identifizieren und die nötigen Schritte einzuleiten. Screenshots sind auch sehr hilfreich. Melde Probleme auf der [http://www.waze.com/support/ Seite "Benutzerunterstützung]. 8481df48623d9cb4c14830a6a8c869b420a4bcae 0 73 11907 2017-04-08T20:56:24Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Die Straßenkarten= Die Waze Basis-Karte (Base Map) wurde in vielen Ländern, durch den Import vo…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Die Straßenkarten= Die Waze Basis-Karte (Base Map) wurde in vielen Ländern, durch den Import von öffentlich verfügbaren Straßendaten in das System generiert. Diese Daten sind ziemlich genau in der Geometrie, sie können aber etwas Bearbeitung gebrauchen. Außerdem nicht enthalten sind: Zulässige Fahrtrichtungen, Abbiegeregeln, Unterscheidung zwischen befahrbaren und nicht befahrbaren Straßen, wie Eisenbahnen und Fußwege. In den importierten Karten wird auch nicht unterschieden zwischen Brücke oder Kreuzung. Standardmässig ist alles mit einer Kreuzung verbunden und braucht daher definitiv Bearbeitung und Pflege. Hier kommen zwei wichtige Aspekte ins Spiel: # Der Karteneditor für die Benutzer, welche die Karten ihrer Stadtteile, Städte oder anderer Orte bearbeiten, mit denen sie vertraut sind. # Das Sammeln von GPS-Daten der App-Benutzer um die Karte automatisiert zu modifizieren, Fahrtrichtungen und Abbiegungen an Kreuzungen zu ermitteln. In einigen Ländern sind keine Basis-Daten verfügbar für die Straßenkarte, die Karten in diesen Ländern müssen von Grund auf neu aufgebaut werden. Sie werden durch die Benutzer im Karteneditor erstellt. Dabei werden aufgezeichnete Straßen der Waze-App und im Karteneditor neugezeichnete Straßen verwendet. Zur Hilfe stehen im Karteneditor gesammelte GPS-Punkte und vielerorts Luftaufnahmen zur Verfügung. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Karteneditor= * Der Standard-Editor für Waze heißt "Waze Map-Editor" oder kurz "WME". * Der WME wurde mit dem internen Codenamen "Papyrus" versehen. * Wenn Du an der Karte arbeitest, bitte [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] beachten. * Mit dem Karteneditor kannst Du alles in einer vordefinierten Gegend bearbeiten. Diese richtet sich nach den [[Rechte_zum_Bearbeiten_der_Karte#Rechte_basierend_auf_Fahrten|Rechten]], die Du bei Deiner Fahrt erwirbst oder der Funktion, die Dir zugesprochen wurde. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Simulation== Du kannst den Karteneditor auch einfach ausprobieren, dafür wurde eine Simulation geschaffen. Deine Änderungen werden nicht übernommen und auch nicht auf der Karte erscheinen. Probiers und schau Dir auch das Video an! Wenn Du den Karteneditor das erste Mal startest, siehst Du folgendes: [[Image:Playmode1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Im Karteneditor anmelden== * Unterstützt wird offiziell der Chrome Browser. Der Karteneditor läuft aber auch mit Firefox oder Safari. '''Die Anmeldung:''' * Anmeldung im Waze-Konto mit dem Benutzernamen auf der Waze-Homepage, der Link zur Anmeldung befindet sich oben rechts auf der Seite https://www.waze.com/de/ * Auswahl des Links "Echtzeit-Karte" in der Haupt-Navigationsleiste * Auswahl des Links "Karteneditor" in der Suchleiste * Du kannst Dich auch direkt im Karteneditor anmelden mit Benutzername und Passwort: https://www.waze.com/de/editor/ * Du kannst den Link auch als Lesezeichen ablegen *Auf der Seite [[WME Tipps und Tricks]] gibt es Informationen dazu. Wenn Du Dich korrekt angemeldet hast, siehst Du folgendes: [[Image:Login1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Start-Position des Karteneditors== Um den Karteneditor an einer bestimmten Stelle zu starten: # Wähle den gewünschten Kartenausschnitt aus. # Klick auf Permalink # Kopiere die URL in der Adressleiste deines Browsers in die Lesezeichen. * So kannst Du ein Gebiet deiner Wahl als Startpunkt des Karteneditors bestimmen. Immer wenn Du den Karteneditor über das Lesezeichen öffnest, wird er Dich genau an diese Stelle bringen. * Der Karteneditor öffnet sich in der Regel an der Stelle, wo Du als letztes gearbeitet hast. Es sei denn Du löschst den Cache deines Browsers. Dann ist der Startpunkt London. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Auswählen der Sprache== Die Sprachauswahl des Karteneditors befindet sich in der oberen, rechten Ecke der Haupt-Navigationsleiste [[File:Sprachauswahl.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Oberfläche und Steuerelemente= ==Aussehen des Karteneditors== Es gibt drei Hauptelemente im Waze Map-Editor: # Die Werkzeugleiste # Die Reiter # Der Anzeigebereich der Karte [[File:Anzeige4.png|700px]] Zuoberst ist die Werkzeugleiste mit einem Suchfeld und Buttons für: Hinzufügen, Speichern, Rückgängig, Wiederholen und Löschen.<br> Auf der linken Seite befinden sich die Reiter. Wenn kein Segment ausgewählt ist, zeigen die Reiter: * '''Ich''' Deinen Benutzernamen, das Total Deiner Punkte, Deine Rechte und einen Link zum Map Editing Video. * '''Fahrten''' Wo Du mit Waze gefahren bist. * '''Gebiete''' Wo Du überall die Karte bearbeiten darfst. Wenn ein Segment ausgewählt ist, zeigen die Reiter: * '''Eigenschaften''' Alle Eigenschaften an, die Du bearbeiten kannst. Straßentyp, Richtung, Level, Mautstraße oder Straßen sperren (Lock) * '''Bearbeiten''' zeigt alle anderen Eigenschaften, wie: Land, Stadt, Straße oder Alternative Straßennamen. *'''Gesamte Straße auswählen''' erlaubt das Auswählen eines gesamten Straßenzugs. *'''Hausnummern bearbeiten''' erlaubt das Bearbeiten von Hausnummern für ein ausgewähltes Segment. Dies ist nur für ein einziges Segment möglich. Oben links unterhalb der Werkzeugleiste befindet sich: * Die Anzeige des aktuellen Orts. Auf der rechten Seite unterhalb der Werkzeugleiste: * Der Lade-Indikator (Karte lädt, Speichern etc.) und die Ebenen-Auswahl. Am unteren Rand des Hauptfensters befindet sich: * In der linken Ecke die Skala des Zoom-Stufen. * In der rechten Ecke die Permalink-Schaltfläche und die Anzeige des Längen- und Breitengrads der aktuellen Maus-Zeiger-Position. Auf der linken Seite unterhalb der Reiter befindet sich eine Schaltfläche mit Links zum Wiki, Forum, Status-Seite und zu den Tastaturkürzeln des Karteneditors.<br> [[File:EditorLinks.png]] Der Anzeigebereich der Karte, welcher die größte Fläche einnimmt, bietet die Möglichkeit zur Anzeige der Luftaufnahmen, Städte, Straßen, Kreuzungen, Orientierungspunkte, Blitzer, GPS-Punkte, Kartenfehler und der Gebiete, die man bearbeiten darf. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Werkzeugleiste== [[Image:WME-Werkzeugleiste.png|700px]] ===Das Suchfeld=== Im Suchfeld kann man Adressen, Städte, Staaten, Länder, Orientierungspunkte oder eine Kombination derer eingeben. Nach Betätigen der Eingabe-Taste oder klicken auf den Such-Button, wird entweder eine Auswahl angezeigt oder nur der gesuchte Ort. Beispiel: Suche nach "Blumenstraße, München" Wird dich an die gewünschte Adresse bringen und setzt einen Marker auf die Karte. [[Image:Suchfeld1.png|700px]] Eine Suche nach "Blumenstraße", zeigt einige Ergebnisse an. [[Image:Suchfeld2.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Hinzufügen=== [[Image:Button-hinzufügen.png|left]] Tastaturkürzel: '''i''', '''o''', '''u''', '''g''' oder '''p''' Der Hinzufügen-Button muss nur mit der Maus berührt werden, und es öffnet sich ein Menü mit den Aktionen. Von hier aus kannst Du Straßen, Kreisverkehre oder Orientierungspunkte etc. hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Speichern=== [[Image:Speichern1.png |left]] [[Image:Speichern2.png]] [[Image:Speichern3.png]] Tatstaturkürzel: '''Ctrl+s''' <br> Der Speichern-Button speichert alle aktuellen Bearbeitungsschritte. Der Button besitzt einen Zähler. 0-9 Bearbeitungsschritte werden in schwarzen Ziffern angezeigt und ab 10 Bearbeitungsschritten erscheinen die Ziffern rot. Wenn es beim Speichern einen Fehler gibt, erscheint ein Fenster mit einer Fehlermeldung, die das Problem normalerweise beschreibt. Der Map-Editor versucht die Stelle auf der Karte anzuzeigen, wo der Fehler liegt und zeigt den Fehler in Form eines hellen Kreises an. Sobald der Speichern-Button angeklickt wird, ist es nicht mehr möglich etwas rückgängig zu machen! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Rückgängig=== [[Image:Button-rueckgaengig.png|left]] Tastaturkürzel: '''Ctrl+Z''' Der Rückgängig-Button macht Schrittweise die Bearbeitungsschritte rückgängig, die '''noch nicht gespeichert''' wurden. <span style="color:red;">Wurde bereits gespeichert, ist es nicht mehr möglich etwas rückgängig zu machen, das man zuvor bearbeitet hat!</span> Ein Bearbeitungsschritt kann das Löschen einer Kreuzung sein, die Benennung einer Straße oder sonstigem. Wenn Du aber 10 Segmente auswählst und gleichzeitig bearbeitest um sie z.B. von "Unknown" auf 2spurig umzustellen, dann gilt dies als ein Bearbeitungsschritt, wenn Du den Rückgängig-Button drückst. Alle 10 Segmente werden dann rückgängig gemacht! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Wiederholen=== [[Image:Button-wiederholen.png|left]] Tastaturkürzel: '''Ctrl+Shift+Z''' Der Wiederholen-Button wiederholt alles, was der Rückgängig-Button zuvor rückgängig gemacht hat. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Löschen=== [[Image:Button-loeschen.png|left]] Tastaturkürzel: '''Delete (Del)''' Der Löschen-Button löscht alles was ausgewählt ist. Sind mehrere Segmente ausgewählt, muss man dies auf einem Popup bestätigen und danach kann gespeichert werden. Das einzige, was im Moment in Mehrfach-Auswahl gelöscht werden kann sind Straßen-Segmente. Der Rückgängig-Button kann auch bereits zur Löschung ausgewählte Objekte wiederherstellen, '''solange nicht gespeichert''' wurde nach dem Löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Reiter== [[File:Hallo.png]] Zuoberst grüßt man dich mit deinem Benutzernamen und zeigt dir das Total deiner Punkte an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Ich=== [[Image:Wazer-rechte.png]] Der Ich-Reiter zeigt einen Wazer mit gelbem Bauhelm, und die entsprechenden Rechte. Sie werden in orangfarbenen Pylonen dargestellt. Weiteres dazu [[Rechte zum Bearbeiten der Karte|hier]]. Darunter wird angezeigt, welche Rechte Du besitzt und das Total Deiner Punkte. Unterhalb der Benutzerinformationen befindet sich diese Schaltfläche: [[File:Benutzer Video.png]] Sie öffnet ein Interface, das 7 Videos über Waze auf Youtube enthält. Diese Videos sind auf Englisch und heißen: # Einführung # Bevor Du beginnst # Erste Schritte # Grundbegriffe # Grundlagen # Kartenfehler # Beispiele Diese animierte Anleitung ist ein guter Weg, um einen Überblick über das System und einige der Prozesse zu bekommen. Diese Videos sind nur eine Einführung. In den Dokumentationen und den [[Main_Page|Waze-Wikis]] sind die meisten Details über den Karteneditor zu finden. Auch wenn es um Richtlinien für Standards und länderspezifische Eigenheiten geht, sind diese unerlässlich. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Fahrten=== Unter "Fahrten" siehst Du die Strecken, die Du mit Waze gefahren bist. Wenn Du einen Eintrag auswählst, zoomt die Karte dahin und zeigt die Strecke innerhalb der Karte an. Oben auf der Karte wird ein Fenster angezeigt, das Dir zeigt, welche Strecke Du gefahren bist. Routen die länger als 20 Meilen/32 Kilometer sind, zeigt der Editor nicht innerhalb der Karte an. Du kannst dann anhand der gefahrenen Strecke eine Straße auf die Karte zeichnen, wenn Du "Straße erstellen" anklickst. Die Straßen, die Du erstellen kannst, zeigt der Streckenverlauf rot an. Erstelle keine Segmente über bereits bestehende Straßen. Schau Dir zuerst die Karte an! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Gebiete=== Diese Liste zeigt definierte Gebiete an, in denen Du arbeiten kannst. Entweder die Gebiete, die Du befahren hast oder die Gebiete in denen Du Area- oder Country-Manager bist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Segmente== [[File:Reiteranzeige.png|right]] [[File:Ausgewaehlt editmodus.png|right]] '''Einzelnes Segment ausgewählt:'''<br> Im oberen Teil werden der Name des Segments und die "Alternativen Straßennamen" angezeigt. Darunter der Bearbeiten-Button. Im unteren Teil wird Straßentyp, Richtung, Ebene und Stufe der Sperre angezeigt. '''Bei Mehrfach-Auswahl:'''<br> Der obere Bereich zeigt an, wie viele Segmente ausgewählt sind. Das Beispiel rechts zeigt, wie die Situation aussieht, wenn 2 Segmente ausgewählt sind im "Bearbeiten-Modus". '''Eigenschaften bearbeiten:'''<br> Wenn Du auf Bearbeiten klickst oder das Tastaturkürzel '''"e"''' drückst, wechselt die Ansicht in den Bearbeiten-Modus und zeigt alle wichtigen Informationen an. Es ermöglicht Dir alle Eigenschaften wie: Landes-, Stadt- und Straßennamen zu ändern. Das Feld für Bundesländer/Kantone resp. Staaten ist im Moment noch den USA vorbehalten. Auch alternative Straßennamen kannst Du bearbeiten. Dies ist dann interessant, wenn die Straße einen lokalen Namen besitzt, der nicht im Hauptfeld des Segments Platz hat, oder nicht offiziell gebräuchlich ist. Beispiel: Die A1 in Österreich hat im alternativen Namen die Bezeichnung "West Autobahn" Oder das Beispiel, das im Screenshot zu sehen ist.<br> '''Das Stadt-Feld des alternativen Namens muss den selben Namen, wie das Stadt-Feld des Segments besitzen.''' <br style="clear: both" /> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Blitzer== [[File:Blitzerausgewaehlt.png|right]] Wenn Du einen Blitzer auswählst, kannst Du diesen an einen beliebigen Ort auf der Karte verschieben. Du musst die Geschwindigkeit erfassen und "Bestätigt" anklicken, um den Blitzer auf der Karte zu aktivieren. Ist ein Blitzer nicht bestätigt, erscheint er auch nicht auf der Karte. Rotlicht-Blitzer brauchen keine Geschwindigkeitsangabe. <br style="clear: both" /> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Orientierungspunkte== {| border="0" cellpadding="2" style="background:none;" |- style="vertical-align:top;" | Wenn Du eine Orientierungspunkt auswählst, kannst Du ihn benennen, einen Orientierungspunkt-Typ vergeben und den Orientierungspunkt mit einer Sperre versehen. Die Sperre hindert Editoren mit niedrigeren Stufen (Rechte) den Orientierungspunkt zu verändern: | | Darunter befinden sich die Adressdetails. ''Klick'' auf '''Bearbeiten''' und ändere die Details, ''klick'' auf '''Übernehmen''', wenn Du alles eingegeben hast: |- style="vertical-align:top;" | [[File:Orientierungspunktausgewaehlt.png]] | | [[File:Orientierungspunktausgewaehltadressdetails.png]] Wird eine korrekte Adresse eingegeben, ermöglichen wir damit Waze, die interne Suche für die Orientierungspunkte zu verwenden und nicht externe Anbieter. |} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Anzeigebereich der Karte= Alle ausgewählten Ebenen sind im Anzeigebereich der Karte zu sehen. Der Anzeigebereich der Karte nimmt den Hauptteil des Browser-Fensters ein. Jedes Objekt, das angezeigt wird ist auswählbar und kann bearbeitet werden. Dies hängt von den Rechten ab, die Du im ausgewählten Kartenausschnitt besitzt. Wähle eine Straße aus und verändere ihre Geometrie. Wähle einen Orientierungspunkt aus und gebe ihm einen Namen. Füge eine Straße hinzu, wo eine sein sollte oder lösche Straßen, die nicht mehr zu sehen sein sollen. Es gibt sieben Hauptbestandteile in den Ecken des Anzeigebereichs auf der Karte: # Die Infoleiste # Die Zoom-Steuerung inkl. Streetview # Die Schaltfläche für den Chat # Die Ebenen-Auswahl # Die Permalink-Schaltfläche # Die Anzeige des Längen- und Breitengrades # Die Zoom-Skala </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Info Leiste== [[File:Infoleiste.png|700px]] Unter dem Suchfeld befindet sich die Info-Leiste. * Links die Stadt und das Land des aktuellen Kartenausschnitts. * Rechts befindet sich eine Box, die nur erscheint, wenn etwas geladen wird. Karte lädt, Speichern, Straßen laden etc. Daneben die Ebenen-Auswahl. Probleme beim Speichern können hauptsächlich beim Verbinden an Kreuzungen und Geometrieänderungen entstehen. Deshalb arbeite sorgfältig, und Du ersparst dir Mehraufwand. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Zoom-Steuerung== [[Image:Zoomregler.png|left]] Tastaturkürzel: '''Shift+UpArrow''', Tastaturkürzel: '''Shift+DownArrow''' In der oberen linken Ecke befindet sich die Zoom-Skala, sie besitzt 10 Stufen. Die Steuerung der Skala + und - kann benutzt werden, um die Karte zu vergrößern oder zu verkleinern. Dies funktioniert auch, wenn der Regler verschoben wird, oder am einfachsten, wenn man am Mausrad dreht. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Streetview== [[Image:Streetview.png]] Direkt unter der Zoom-Steuerung befindet sich der Streetview. Ziehe die blaue Linse auf die Straße, die Du im Streetview anschauen möchtest. Der Streeview ist nicht überall vorhanden, er hängt davon ab, was uns Google zur Verfügung stellt. [[Image:Streetview-nicht-vorhanden.png|left]] Wo kein Streetview verfügbar ist, bleibt die Linse beim Ziehen über der Karte rot. <br style="clear: both" /> [[Image:Streetview-vorhanden.png|left]] Wo der Streetview verfügbar ist, färbt sich die Linse beim Ziehen über der Karte blau, Du kannst die Linse loslassen und die Straße im Streetview anschauen. <br style="clear: both" /> Wenn Du die Linse losgelassen hast, enthält sie einen Pfeil, der in die Richtung des Streetviews zeigt. [[Image:Wme streetview directional arrow.gif]] Während des Streetviews sind alle anderen Operationen möglich (Segment-Eigenschaften, Kartenfehler und Aktualisierungsanfragen, Hausnummern, zeitliche Beschränkungen etc.) Die Rechte Seite des Fensters enthält den Streetview. Du kannst die Ansicht in alle Richtungen verschieben mit der Maus, oder mit der Steuerung oben links im Streetview-Fenster. Zoomen kannst Du über den Regler oder mit dem Mausrad. Um die Position der Ansicht zu verschieben, kannst Du auf die Pfeile unterhalb der Bildmitte klicken oder Dich per Mausklick fortbewegen. Du kannst auch die Linse auf der Karte verschieben, mit dem kleinen weißen Punkt darunter. [[Image:Streetview-situation.png|700px]] Wenn Du zu viel auf einmal aktivierst, wirst Du feststellen, dass der bearbeitbare Bereich auf der Karte immer kleiner wird. Z.B. eine Aktualisierungsanfrage mit dem Fenster für Kommentare. Denke an die Tastaturkürzel, denn der Zoom-Regler der Karte ist dann verdeckt und somit kannst Du nur noch mit den Tastaturkürzeln Zoomen. Um den Streetview zu beenden, klicke auf das X in der oberen, rechten Ecke des Streetview-Fensters. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Der Editor-Chat== Wird demnächst erstellt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ebenen-Auswahl== Auf der rechten Seite der Karte findest Du dieses Symbol: [[Image:Layers-Auswahl.png]] Wenn Du mit der Maus darüber fährst, zeigt es Dir an, welche Ebenen aktuell ausgewählt sind. Die Ebenen mit den vier Punkten vor dem Namen, kannst Du in der Auswahl beliebig anordnen. [[WME_Schnellstart-Anleitung#Tastaturk.C3.BCrzel|'''Tastaturkürzel''']]. [[File:Ebenen.png]] Hier ein paar Informationen dazu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Die Luftaufnahmen=== [[Image:Aerial_skinny.png|260px]] Tastaturkürzel: '''Shift+b''' Waze benutzt Luftaufnahmen von Google (oder VirtualEarth). </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Städte=== [[Image:cities_skinny.png|260px]] Tastaturkürzel: '''Shift+c''' Diese Ebene zeigt die Grenzen der Städte verschiedenfarbig an in Form von Polygonen. Je nachdem, wie die Segmente benannt wurden. Dies ist hilfreich, um falsch benannte Segmente zu identifizieren. Manchmal können die Grenzen überlappen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Straßen=== [[Image:Road_segments_skinny.png|260px]] Tastaturkürzel: '''Shift+r''' In der Ebene sind die Straßen, Gassen, Autobahnen etc., aus denen sich die fahrbare Karte des Systems in Waze zusammensetzt. Je nach Zoom-Stufe sind einige Straßen nicht sichtbar, damit die Karte nicht zu unübersichtlich dargestellt wird. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===GPS-Punkte=== [[Image:Gps_tracks_straight_skinny.png|260px]] Tastaturkürzel: '''Shift+g''' Diese Ebene zeigt die GPS-Punkte der Benutzer an, die mit der Waze-App herumgefahren sind. Waze zeichnet die GPS-Koordinaten der Fahrer auf und wandelt sie in farbige Pfeile um, diese sind dann in der Karte sichtbar. Diese Ebene ist sehr hilfreich, um Straßen auf der Karte an richtiger Stelle zu platzieren, wenn z.B. keine Luftbilder vorhanden sind. Die Pfeile haben unterschiedliche Farben in jeder Fahrtrichtung. Das macht es einfacher, fehlerhafte GPS-Spuren zu lokalisieren oder Straßen auf der Karte zu finden, die nicht dem tatsächlichen Straßenverlauf folgen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Area-Manager=== Zeigt die Area-Manager im ausgewählten Ausschnitt an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Orientierungspunkte=== [[Image:Landmarks_skinny.png|260px]] Tastaturkürzel: '''Shift+l''' Orientierungspunkte sind auch unter Landmarks oder POI's (Points of Interest) bekannt. Diese können für nahezu alles verwendet werden: Tankstellen, Parks, Flüsse. Friedhöfe etc. Mehr Informationen zu den Orientierungspunkten findest Du [[Erstellen und bearbeiten von Landmarks|hier]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Blitzer=== [[Image:Speed_cam_enabled.png]] [[Image:Red-light_cam_enabled.png]] [[File:Fakeblitzer.png]] Tastaturkürzel: '''Shift+s''' In dieser Ebene kann man Geschwindigkeits-, Rotlicht- und Fake-Blitzer anzeigen lassen. Wer mit Waze durch die Straßen fährt, kann über die Anwendung Blitzer melden. Die Blitzer müssen im Karteneditor bearbeitet und bestätigt werden. Vorher erscheinen sie nicht auf der Anwendung. Bestätigte Blitzer warnen optisch und akustisch während der Fahrt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ====Geschwindigkeits-Blitzer==== Diese Blitzer sind fest montierte Blitzer im Straßenverkehr und blitzen die Fahrer bei Geschwindigkeitsübertretung. Die Blitzer in Waze blitzen in die Fahrtrichtung, das heißt: Will man gewarnt werden, muss man den roten Punkt im Karteneditor der Fahrtrichtung entlang ausrichten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ====Rotlicht-Blitzer==== Diese Blitzer sind fest montierte Rotlicht-Blitzer. Diese blitzen, wenn ein Rotlicht missachtet wird. Rotlicht-Blitzer in Waze warnen nur aus einer Richtung, das heißt: Will man von 4 Seiten her gewarnt werden, müssen 4 Blitzer positioniert werden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ====Fake-Blitzer==== Fake-Blitzer sind Attrappen, die nur so aussehen wie ein richtiger Blitzer und sollen den Fahrer zur Vorsicht bewegen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Kartenfehler=== [[Image:Problem_pin_open-low.gif|left]][[Image:Problem_pin_open-med.gif]] [[Image:Problem_pin_open-high.gif]] Tastaturkürzel: '''Shift+p''' <br> Der Waze-Server analysiert laufend die GPS-Daten, um Fehler zu erkennen. Diese werden dann über die Ebene Kartenfehler sichtbar. Sie sollen den Benutzer, der die Karte bearbeitet darauf hinweisen, dass die Karte Fehler aufweist, die es zu bearbeiten gilt. Typische Kartenfehler sind: Fehlende Straßen, falsche Abbiegungen, falsche Einbahnstraßen oder fehlende Verbindungen zwischen Segmenten. Für Informationen, lies [[WME Map Problems]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Aktualisierungsanfragen=== [[Image:Request_pin_open-low.gif|left]][[Image:Request_pin_open-med.gif]] [[Image:Request_pin_open-high.gif]] Tastaturkürzel: '''Shift+u''' <br> Die Aktualisierungsanfragen werden von den Benutzern der Waze-App während der Fahrt oder auf der "Echtzeit-Karte" gemeldet. * Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei gefahren ist, zeigt die Ebene im Karteneditor hellgrün an. * Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei während der Navigation gefahren ist, zeigt die Ebene im Karteneditor lila an mit den Abbiege-Anweisungen, die der Benutzer dabei erhalten hat. * Für Informationen, lies [[WME Update Requests]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Meine Gebiete=== [[Image:Editable_area_skinny.png|260px]] Tastaturkürzel: '''Shift+e''' Wo Du die Karte bearbeiten kannst, hängt davon ab, wo Du mit der Waze-App gefahren bist. Die Rechte sind im Umkreis von 1 Meile bzw. 1,6 Kilometer um die befahrene Strecke vorhanden. Die Gebiete die Du bearbeiten kannst, zeigen sich im Karteneditor wie folgt: * Hell hinterlegt sind Gebiete, die Du mit Waze befahren hast. * Die farbigen Gebiete sind die, in denen Du Area-Manager bist. * Dunkle Gebiete kannst Du nicht bearbeiten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Permalink-Schaltfläche== [[Image:Permalink-neu.png]] Außerhalb der Karte unten rechts befindet sich die Permalink-Schaltfläche. Der Permalink ändert immer dann, wenn die Karte verschoben wird, Objekte ausgewählt oder deselektiert werden. Man beachte: Der Permalink wird nicht jedesmal automatisch neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn man eine Browser-Sitzung wiederherstellt inkl. Editor, wird der Browser die letzte Kartenposition des Permalinks anzeigen, den man zuvor generiert hat. Wenn man Permalink anklickt, speichert dieser alle Informationen für den ausgewählten Kartenausschnitt. Man kann ihn anklicken, um die Karte zu aktualisieren, mit einem Rechtsklick kopieren, mit anderen Benutzern im Forum teilen oder als Lesezeichen ablegen. Vor allem bei Fragen zur Karte wird der Permalink im Forum oft gebraucht. Denn er speichert auch ausgewählte Straßen, Kreuzungen und Landmarks, so zeigt er anderen Benutzern schnell, was gemeint ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Anzeige des Längen- und Breitengrades== [[Image:Koordinaten.png]] In der unteren rechten Ecke befindet sich die Anzeige des Längen- und Breitengrades. Sie zeigt den aktuellen Ort, wo der Mauszeiger gerade hinzeigt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Zoom-Skala== {| style="float:left; background: transparent;" width="400" | [[Image:Zoom-Skala.png|left]] |- |Unten rechts befindet sich die Anzeige der Zoom-Stufe. Die Werte in der Skala rechts entsprechen auch der [[#Zoom-Steuerung | Zoomstufe]], die Du in der URL des Browsers siehst (zoom=5). Änderst Du die Zoomstufe darin, verändert sich auch die Ansicht. |} {| style="float:right;" | [[Image:Stufenscala.png]] |} {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karteneditor Steuerung= * Bewege die Karte, indem Du sie mit der Maus umherziehst. * Mit den Pfeiltasten kannst Du die Karte in alle vier Richtungen verschieben. * Es gibt vier Möglichkeiten die Karte zu zoomen: # Über die Zoom-Steuerung am linken oberen Rand der Karte. Regler hoch oder runterziehen mit der Maus oder klicke auf die + oder - Buttons. # Ein Doppelklick auf der Karte zoomt die Karte um eine Stufe rein und zentriert den Ausschnitt an den Ort, wohin man geklickt hat. # Am Mausrad drehen. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. Auf dem Mac mit einem Trackpad oder ähnlichem, nach links und rechts ziehen bewirkt das selbe. # Die ''Shift'' Taste drücken und ein Rechteck auf der Karte Zeichnen. Die Karte zoomt den ausgewählten Auschnitt ein: [[Image:Shift_zoom.png|500px|center]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =WME Schnell-Start Anleitung= Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Um die besten Techniken zu kennen und anzuwenden, braucht ein bisschen Zeit. Aber es kann auch Spaß machen mit wachsender Erfahrung. Man kann Stolz sein darauf, die Anwendung mit ein paar einfachen Bearbeitungsschritten für alle Endbenutzer zu verbessern. Die Links später in dieser Anleitung sind sehr wichtig, um alles zu erlernen was es braucht. Für die einfache Bearbeitung gibt es hier die [[WME Schnellstart-Anleitung]] um sich schnell zurecht zu finden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Permalink= : [[Image:wme permalink highlight.jpg]] * Im Karteneditor ist der [[Glossar#Permalink|Permalink]] eine URL, die Dich direkt an einen spezifischen Punkt auf der Karte bringt. Er speichert Längen- und Breitengrad, Zoom Stufe und alle Sichtbaren Objekte die während der Bearbeitung aktiv sind auf der Karte (ausgewählt in den Ebenen). Um genau auf ein Problem hinzuweisen sollte das betreffende Objekt ausgewählt sein, dies wird nämlich auch gespeichert. * Nach dem Klick auf Permalink unten rechts im Karteneditor, findest Du die Adresse zum Link in der Adresszeile des Browsers. Diese kann kopiert und in Foren-Beiträgen oder Lesezeichen eingefügt werden. Dies funktioniert auch wenn Du Permalink mit der rechten Maustaste auswählt und die Adresse direkt kopierst. * Hinweis: Der Permalink wird nicht jedesmal neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn Du eine Browser Sitzung wiederherstellst inkl. Editor, wird der Browser die letzte Karten-Position des Permalinks anzeigen, den Du zuvor generiert hast. * Falls die Straßen nicht mit den Luftaufnahmen übereinstimmen oder eine ungewöhnliche Position aufweisen, kannst Du mit dem Permalink die Seite aktualisieren, was das Problem in der Regel löst. * Was andere Editoren im Permalink sehen können, hängt von den Rechten ab, die sie besitzen. Ein Editor kann Aktualisierungsanfragen (Update Requests) oder Kartenfehler (Map Problems) nur in seinem bearbeitbaren Gebiet sehen. Also die lokalen Editoren, Area-Manager oder Country-Manager der betreffenden Gebiete oder Länder. Wenn Du ein breiteres Publikum betreffend eines Problems erreichen willst, musst Du ein Bildschirmfoto posten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Permalink in der Echtzeitkarte= Willst Du einen Permalink in der Echtzeitkarte generieren, musst Du auf die Permalink-Schaltfläche in der unteren, rechten Ecke der Karte klicken. Routen werden dabei auch gespeichert. *[[Image:PermalinkLiveMap.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tastaturkürzel= Der Einfachheit halber sind alle Kürzel im [[WME_Schnellstart-Anleitung#Tatstaturk.C3.BCrzel|WME Schnellstart-Anleitung]] an einem Ort zusammengefasst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karten Aktualisierung= Alles was bearbeitet wurde mit dem Karteneditor, wird früher oder später auf der Live Map und in der Waze-App zu sehen sein. Das Ziel von Waze ist es, alle Daten innerhalb von 24 Stunden zu aktualisieren. Dies kann auch mal länger dauern, schau Dir deshalb auch die Seite [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] an. * Die Aktualisierungen und sonstige Ereignisse, werden auch auf der [http://status.waze.com/ Status-Seite] von Waze publiziert. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Einsatz von externen Quellen (wie Google Imagery)= Die Verwendung von beliebigen externen, urheberrechtlich geschützten Informationsquellen, um Informationen in die Datenbank oder die Waze-Karten einzupflegen, ist nicht erlaubt. Externe urheberrechtlich geschützte Informationsquellen beinhaltet alle Online- oder gedruckten Karteninformationen, die nicht von Waze durch die Schnittstelle des Karteneditors bereitgestellt werden. Mit der Akquisition von Waze durch Google, Inc., wurde der Karteneditor von Waze mit Luftaufnahmen von Google und dem Streetview aktualisiert. Diese gelten als interne Quellen und dürfen daher verwendet werden, um Karteninformationen zur Waze-Karte hinzuzufügen. Googles Nutzungsbedingungen binden die Nutzung ihrer Karteninformationen an spezifische Bedingungen und Waze besitzt nur die ordnungsgemäße Lizenz, das was im Karteneditor zu sehen ist auch zu nutzen, aber sonst nichts anderes von Google. Die Verwendung von externen, urheberrechtlich geschützten Quellen gefährden die Karten und Waze wird dadurch gezwungen, alle Änderungen zu löschen und den Urzustand der Karte wieder herzustellen. Dies betrifft alle Änderung des betreffenden Benutzers auf der ganzen Karte! Wenn Du Karten in der Form erstellst, sieht sich Waze leider gezwungen, Deine ganze Arbeit von der Karte zu löschen. So ist es bereits in Chile und anderen Südamerikanischen Ländern passiert aufgrund der Lizenzprobleme. (kein Fehler seitens Waze!) Du darfst gerne mit lokalen Anbietern oder Behörden kommunizieren um allf. Luftaufnahmen oder Informationen zu erhalten, die verwendet werden dürfen. Du musst allerdings dabei klar erwähnen, dass Du nicht für Waze arbeitest oder in Auftrag von Waze handelst. Aber als interessierter Bürger kannst Du natürlich mit den lokalen Behörden sprechen, um die Vorteile für die Allgemeinheit zu erklären, z.B Luftaufnahmen als öffentliches Gut frei zur Verfügung zu stellen. Bei Fragen oder wenn Du nicht sicher bist, kommuniziere unbedingt mit dem Waze-Support. Beachte, dass externe Urheberrechtsinformationen keine Informationsquellen beinhalten, die von Waze durch die internen Werkzeuge des Karteneditors oder der Waze-App zur Verfügung gestellt werden. Auch alle Informationen, die selbstständig von einem Benutzer entwickelt wurden und physisch an einer Stelle abrufbar sind, werden akzeptiert, um damit die Karte zu bearbeiten, solange es nicht urheberrechtlich geschützt zur Verfügung gestellt wurde. Du darfst mit dem Support reden, wenn Du eine Quelle benutzen möchtest und nicht sicher bist, ob Du sie auch verwenden darfst. Waze wird die Quelle prüfen und Dir mitteilen, ob Du sie verwenden darfst oder nicht. Wenn nicht klar ist, ob eine Verwendung Legal ist, gelten die nachfolgenden Verbote. '''Folgendes ist Verboten:''' *Nachschauen ob der Straßenname korrekt ist. *Straßennamen von anderen Karten abtippen. *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren (manuell). *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren mit einem Skript. '''Es ist sehr einfach:''' *Verwende den Karteneditor mit den Möglichkeiten, die innerhalb Waze angeboten werden. *Vermeide alles andere, sofern nicht geprüft und bestätigt von Waze. Darum zeigt Waze im Karteneditor nur die Streetview Bilder ohne zusätzliche Daten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 4b410a2ae13ca56584dea9b9b93e6d3156b4f8d9 11908 11907 2017-04-08T20:58:17Z Popel22 24 /* Ausgewählte Blitzer */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Die Straßenkarten= Die Waze Basis-Karte (Base Map) wurde in vielen Ländern, durch den Import von öffentlich verfügbaren Straßendaten in das System generiert. Diese Daten sind ziemlich genau in der Geometrie, sie können aber etwas Bearbeitung gebrauchen. Außerdem nicht enthalten sind: Zulässige Fahrtrichtungen, Abbiegeregeln, Unterscheidung zwischen befahrbaren und nicht befahrbaren Straßen, wie Eisenbahnen und Fußwege. In den importierten Karten wird auch nicht unterschieden zwischen Brücke oder Kreuzung. Standardmässig ist alles mit einer Kreuzung verbunden und braucht daher definitiv Bearbeitung und Pflege. Hier kommen zwei wichtige Aspekte ins Spiel: # Der Karteneditor für die Benutzer, welche die Karten ihrer Stadtteile, Städte oder anderer Orte bearbeiten, mit denen sie vertraut sind. # Das Sammeln von GPS-Daten der App-Benutzer um die Karte automatisiert zu modifizieren, Fahrtrichtungen und Abbiegungen an Kreuzungen zu ermitteln. In einigen Ländern sind keine Basis-Daten verfügbar für die Straßenkarte, die Karten in diesen Ländern müssen von Grund auf neu aufgebaut werden. Sie werden durch die Benutzer im Karteneditor erstellt. Dabei werden aufgezeichnete Straßen der Waze-App und im Karteneditor neugezeichnete Straßen verwendet. Zur Hilfe stehen im Karteneditor gesammelte GPS-Punkte und vielerorts Luftaufnahmen zur Verfügung. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Karteneditor= * Der Standard-Editor für Waze heißt "Waze Map-Editor" oder kurz "WME". * Der WME wurde mit dem internen Codenamen "Papyrus" versehen. * Wenn Du an der Karte arbeitest, bitte [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] beachten. * Mit dem Karteneditor kannst Du alles in einer vordefinierten Gegend bearbeiten. Diese richtet sich nach den [[Rechte_zum_Bearbeiten_der_Karte#Rechte_basierend_auf_Fahrten|Rechten]], die Du bei Deiner Fahrt erwirbst oder der Funktion, die Dir zugesprochen wurde. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Simulation== Du kannst den Karteneditor auch einfach ausprobieren, dafür wurde eine Simulation geschaffen. Deine Änderungen werden nicht übernommen und auch nicht auf der Karte erscheinen. Probiers und schau Dir auch das Video an! Wenn Du den Karteneditor das erste Mal startest, siehst Du folgendes: [[Image:Playmode1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Im Karteneditor anmelden== * Unterstützt wird offiziell der Chrome Browser. Der Karteneditor läuft aber auch mit Firefox oder Safari. '''Die Anmeldung:''' * Anmeldung im Waze-Konto mit dem Benutzernamen auf der Waze-Homepage, der Link zur Anmeldung befindet sich oben rechts auf der Seite https://www.waze.com/de/ * Auswahl des Links "Echtzeit-Karte" in der Haupt-Navigationsleiste * Auswahl des Links "Karteneditor" in der Suchleiste * Du kannst Dich auch direkt im Karteneditor anmelden mit Benutzername und Passwort: https://www.waze.com/de/editor/ * Du kannst den Link auch als Lesezeichen ablegen *Auf der Seite [[WME Tipps und Tricks]] gibt es Informationen dazu. Wenn Du Dich korrekt angemeldet hast, siehst Du folgendes: [[Image:Login1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Start-Position des Karteneditors== Um den Karteneditor an einer bestimmten Stelle zu starten: # Wähle den gewünschten Kartenausschnitt aus. # Klick auf Permalink # Kopiere die URL in der Adressleiste deines Browsers in die Lesezeichen. * So kannst Du ein Gebiet deiner Wahl als Startpunkt des Karteneditors bestimmen. Immer wenn Du den Karteneditor über das Lesezeichen öffnest, wird er Dich genau an diese Stelle bringen. * Der Karteneditor öffnet sich in der Regel an der Stelle, wo Du als letztes gearbeitet hast. Es sei denn Du löschst den Cache deines Browsers. Dann ist der Startpunkt London. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Auswählen der Sprache== Die Sprachauswahl des Karteneditors befindet sich in der oberen, rechten Ecke der Haupt-Navigationsleiste [[File:Sprachauswahl.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Oberfläche und Steuerelemente= ==Aussehen des Karteneditors== Es gibt drei Hauptelemente im Waze Map-Editor: # Die Werkzeugleiste # Die Reiter # Der Anzeigebereich der Karte [[File:Anzeige4.png|700px]] Zuoberst ist die Werkzeugleiste mit einem Suchfeld und Buttons für: Hinzufügen, Speichern, Rückgängig, Wiederholen und Löschen.<br> Auf der linken Seite befinden sich die Reiter. Wenn kein Segment ausgewählt ist, zeigen die Reiter: * '''Ich''' Deinen Benutzernamen, das Total Deiner Punkte, Deine Rechte und einen Link zum Map Editing Video. * '''Fahrten''' Wo Du mit Waze gefahren bist. * '''Gebiete''' Wo Du überall die Karte bearbeiten darfst. Wenn ein Segment ausgewählt ist, zeigen die Reiter: * '''Eigenschaften''' Alle Eigenschaften an, die Du bearbeiten kannst. Straßentyp, Richtung, Level, Mautstraße oder Straßen sperren (Lock) * '''Bearbeiten''' zeigt alle anderen Eigenschaften, wie: Land, Stadt, Straße oder Alternative Straßennamen. *'''Gesamte Straße auswählen''' erlaubt das Auswählen eines gesamten Straßenzugs. *'''Hausnummern bearbeiten''' erlaubt das Bearbeiten von Hausnummern für ein ausgewähltes Segment. Dies ist nur für ein einziges Segment möglich. Oben links unterhalb der Werkzeugleiste befindet sich: * Die Anzeige des aktuellen Orts. Auf der rechten Seite unterhalb der Werkzeugleiste: * Der Lade-Indikator (Karte lädt, Speichern etc.) und die Ebenen-Auswahl. Am unteren Rand des Hauptfensters befindet sich: * In der linken Ecke die Skala des Zoom-Stufen. * In der rechten Ecke die Permalink-Schaltfläche und die Anzeige des Längen- und Breitengrads der aktuellen Maus-Zeiger-Position. Auf der linken Seite unterhalb der Reiter befindet sich eine Schaltfläche mit Links zum Wiki, Forum, Status-Seite und zu den Tastaturkürzeln des Karteneditors.<br> [[File:EditorLinks.png]] Der Anzeigebereich der Karte, welcher die größte Fläche einnimmt, bietet die Möglichkeit zur Anzeige der Luftaufnahmen, Städte, Straßen, Kreuzungen, Orientierungspunkte, Blitzer, GPS-Punkte, Kartenfehler und der Gebiete, die man bearbeiten darf. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Werkzeugleiste== [[Image:WME-Werkzeugleiste.png|700px]] ===Das Suchfeld=== Im Suchfeld kann man Adressen, Städte, Staaten, Länder, Orientierungspunkte oder eine Kombination derer eingeben. Nach Betätigen der Eingabe-Taste oder klicken auf den Such-Button, wird entweder eine Auswahl angezeigt oder nur der gesuchte Ort. Beispiel: Suche nach "Blumenstraße, München" Wird dich an die gewünschte Adresse bringen und setzt einen Marker auf die Karte. [[Image:Suchfeld1.png|700px]] Eine Suche nach "Blumenstraße", zeigt einige Ergebnisse an. [[Image:Suchfeld2.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Hinzufügen=== [[Image:Button-hinzufügen.png|left]] Tastaturkürzel: '''i''', '''o''', '''u''', '''g''' oder '''p''' Der Hinzufügen-Button muss nur mit der Maus berührt werden, und es öffnet sich ein Menü mit den Aktionen. Von hier aus kannst Du Straßen, Kreisverkehre oder Orientierungspunkte etc. hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Speichern=== [[Image:Speichern1.png |left]] [[Image:Speichern2.png]] [[Image:Speichern3.png]] Tatstaturkürzel: '''Ctrl+s''' <br> Der Speichern-Button speichert alle aktuellen Bearbeitungsschritte. Der Button besitzt einen Zähler. 0-9 Bearbeitungsschritte werden in schwarzen Ziffern angezeigt und ab 10 Bearbeitungsschritten erscheinen die Ziffern rot. Wenn es beim Speichern einen Fehler gibt, erscheint ein Fenster mit einer Fehlermeldung, die das Problem normalerweise beschreibt. Der Map-Editor versucht die Stelle auf der Karte anzuzeigen, wo der Fehler liegt und zeigt den Fehler in Form eines hellen Kreises an. Sobald der Speichern-Button angeklickt wird, ist es nicht mehr möglich etwas rückgängig zu machen! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Rückgängig=== [[Image:Button-rueckgaengig.png|left]] Tastaturkürzel: '''Ctrl+Z''' Der Rückgängig-Button macht Schrittweise die Bearbeitungsschritte rückgängig, die '''noch nicht gespeichert''' wurden. <span style="color:red;">Wurde bereits gespeichert, ist es nicht mehr möglich etwas rückgängig zu machen, das man zuvor bearbeitet hat!</span> Ein Bearbeitungsschritt kann das Löschen einer Kreuzung sein, die Benennung einer Straße oder sonstigem. Wenn Du aber 10 Segmente auswählst und gleichzeitig bearbeitest um sie z.B. von "Unknown" auf 2spurig umzustellen, dann gilt dies als ein Bearbeitungsschritt, wenn Du den Rückgängig-Button drückst. Alle 10 Segmente werden dann rückgängig gemacht! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Wiederholen=== [[Image:Button-wiederholen.png|left]] Tastaturkürzel: '''Ctrl+Shift+Z''' Der Wiederholen-Button wiederholt alles, was der Rückgängig-Button zuvor rückgängig gemacht hat. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Löschen=== [[Image:Button-loeschen.png|left]] Tastaturkürzel: '''Delete (Del)''' Der Löschen-Button löscht alles was ausgewählt ist. Sind mehrere Segmente ausgewählt, muss man dies auf einem Popup bestätigen und danach kann gespeichert werden. Das einzige, was im Moment in Mehrfach-Auswahl gelöscht werden kann sind Straßen-Segmente. Der Rückgängig-Button kann auch bereits zur Löschung ausgewählte Objekte wiederherstellen, '''solange nicht gespeichert''' wurde nach dem Löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Reiter== [[File:Hallo.png]] Zuoberst grüßt man dich mit deinem Benutzernamen und zeigt dir das Total deiner Punkte an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Ich=== [[Image:Wazer-rechte.png]] Der Ich-Reiter zeigt einen Wazer mit gelbem Bauhelm, und die entsprechenden Rechte. Sie werden in orangfarbenen Pylonen dargestellt. Weiteres dazu [[Rechte zum Bearbeiten der Karte|hier]]. Darunter wird angezeigt, welche Rechte Du besitzt und das Total Deiner Punkte. Unterhalb der Benutzerinformationen befindet sich diese Schaltfläche: [[File:Benutzer Video.png]] Sie öffnet ein Interface, das 7 Videos über Waze auf Youtube enthält. Diese Videos sind auf Englisch und heißen: # Einführung # Bevor Du beginnst # Erste Schritte # Grundbegriffe # Grundlagen # Kartenfehler # Beispiele Diese animierte Anleitung ist ein guter Weg, um einen Überblick über das System und einige der Prozesse zu bekommen. Diese Videos sind nur eine Einführung. In den Dokumentationen und den [[Main_Page|Waze-Wikis]] sind die meisten Details über den Karteneditor zu finden. Auch wenn es um Richtlinien für Standards und länderspezifische Eigenheiten geht, sind diese unerlässlich. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Fahrten=== Unter "Fahrten" siehst Du die Strecken, die Du mit Waze gefahren bist. Wenn Du einen Eintrag auswählst, zoomt die Karte dahin und zeigt die Strecke innerhalb der Karte an. Oben auf der Karte wird ein Fenster angezeigt, das Dir zeigt, welche Strecke Du gefahren bist. Routen die länger als 20 Meilen/32 Kilometer sind, zeigt der Editor nicht innerhalb der Karte an. Du kannst dann anhand der gefahrenen Strecke eine Straße auf die Karte zeichnen, wenn Du "Straße erstellen" anklickst. Die Straßen, die Du erstellen kannst, zeigt der Streckenverlauf rot an. Erstelle keine Segmente über bereits bestehende Straßen. Schau Dir zuerst die Karte an! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Gebiete=== Diese Liste zeigt definierte Gebiete an, in denen Du arbeiten kannst. Entweder die Gebiete, die Du befahren hast oder die Gebiete in denen Du Area- oder Country-Manager bist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Segmente== [[File:Reiteranzeige.png|right]] [[File:Ausgewaehlt editmodus.png|right]] '''Einzelnes Segment ausgewählt:'''<br> Im oberen Teil werden der Name des Segments und die "Alternativen Straßennamen" angezeigt. Darunter der Bearbeiten-Button. Im unteren Teil wird Straßentyp, Richtung, Ebene und Stufe der Sperre angezeigt. '''Bei Mehrfach-Auswahl:'''<br> Der obere Bereich zeigt an, wie viele Segmente ausgewählt sind. Das Beispiel rechts zeigt, wie die Situation aussieht, wenn 2 Segmente ausgewählt sind im "Bearbeiten-Modus". '''Eigenschaften bearbeiten:'''<br> Wenn Du auf Bearbeiten klickst oder das Tastaturkürzel '''"e"''' drückst, wechselt die Ansicht in den Bearbeiten-Modus und zeigt alle wichtigen Informationen an. Es ermöglicht Dir alle Eigenschaften wie: Landes-, Stadt- und Straßennamen zu ändern. Das Feld für Bundesländer/Kantone resp. Staaten ist im Moment noch den USA vorbehalten. Auch alternative Straßennamen kannst Du bearbeiten. Dies ist dann interessant, wenn die Straße einen lokalen Namen besitzt, der nicht im Hauptfeld des Segments Platz hat, oder nicht offiziell gebräuchlich ist. Beispiel: Die A1 in Österreich hat im alternativen Namen die Bezeichnung "West Autobahn" Oder das Beispiel, das im Screenshot zu sehen ist.<br> '''Das Stadt-Feld des alternativen Namens muss den selben Namen, wie das Stadt-Feld des Segments besitzen.''' <br style="clear: both" /> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Orientierungspunkte== {| border="0" cellpadding="2" style="background:none;" |- style="vertical-align:top;" | Wenn Du eine Orientierungspunkt auswählst, kannst Du ihn benennen, einen Orientierungspunkt-Typ vergeben und den Orientierungspunkt mit einer Sperre versehen. Die Sperre hindert Editoren mit niedrigeren Stufen (Rechte) den Orientierungspunkt zu verändern: | | Darunter befinden sich die Adressdetails. ''Klick'' auf '''Bearbeiten''' und ändere die Details, ''klick'' auf '''Übernehmen''', wenn Du alles eingegeben hast: |- style="vertical-align:top;" | [[File:Orientierungspunktausgewaehlt.png]] | | [[File:Orientierungspunktausgewaehltadressdetails.png]] Wird eine korrekte Adresse eingegeben, ermöglichen wir damit Waze, die interne Suche für die Orientierungspunkte zu verwenden und nicht externe Anbieter. |} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Anzeigebereich der Karte= Alle ausgewählten Ebenen sind im Anzeigebereich der Karte zu sehen. Der Anzeigebereich der Karte nimmt den Hauptteil des Browser-Fensters ein. Jedes Objekt, das angezeigt wird ist auswählbar und kann bearbeitet werden. Dies hängt von den Rechten ab, die Du im ausgewählten Kartenausschnitt besitzt. Wähle eine Straße aus und verändere ihre Geometrie. Wähle einen Orientierungspunkt aus und gebe ihm einen Namen. Füge eine Straße hinzu, wo eine sein sollte oder lösche Straßen, die nicht mehr zu sehen sein sollen. Es gibt sieben Hauptbestandteile in den Ecken des Anzeigebereichs auf der Karte: # Die Infoleiste # Die Zoom-Steuerung inkl. Streetview # Die Schaltfläche für den Chat # Die Ebenen-Auswahl # Die Permalink-Schaltfläche # Die Anzeige des Längen- und Breitengrades # Die Zoom-Skala </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Info Leiste== [[File:Infoleiste.png|700px]] Unter dem Suchfeld befindet sich die Info-Leiste. * Links die Stadt und das Land des aktuellen Kartenausschnitts. * Rechts befindet sich eine Box, die nur erscheint, wenn etwas geladen wird. Karte lädt, Speichern, Straßen laden etc. Daneben die Ebenen-Auswahl. Probleme beim Speichern können hauptsächlich beim Verbinden an Kreuzungen und Geometrieänderungen entstehen. Deshalb arbeite sorgfältig, und Du ersparst dir Mehraufwand. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Zoom-Steuerung== [[Image:Zoomregler.png|left]] Tastaturkürzel: '''Shift+UpArrow''', Tastaturkürzel: '''Shift+DownArrow''' In der oberen linken Ecke befindet sich die Zoom-Skala, sie besitzt 10 Stufen. Die Steuerung der Skala + und - kann benutzt werden, um die Karte zu vergrößern oder zu verkleinern. Dies funktioniert auch, wenn der Regler verschoben wird, oder am einfachsten, wenn man am Mausrad dreht. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Streetview== [[Image:Streetview.png]] Direkt unter der Zoom-Steuerung befindet sich der Streetview. Ziehe die blaue Linse auf die Straße, die Du im Streetview anschauen möchtest. Der Streeview ist nicht überall vorhanden, er hängt davon ab, was uns Google zur Verfügung stellt. [[Image:Streetview-nicht-vorhanden.png|left]] Wo kein Streetview verfügbar ist, bleibt die Linse beim Ziehen über der Karte rot. <br style="clear: both" /> [[Image:Streetview-vorhanden.png|left]] Wo der Streetview verfügbar ist, färbt sich die Linse beim Ziehen über der Karte blau, Du kannst die Linse loslassen und die Straße im Streetview anschauen. <br style="clear: both" /> Wenn Du die Linse losgelassen hast, enthält sie einen Pfeil, der in die Richtung des Streetviews zeigt. [[Image:Wme streetview directional arrow.gif]] Während des Streetviews sind alle anderen Operationen möglich (Segment-Eigenschaften, Kartenfehler und Aktualisierungsanfragen, Hausnummern, zeitliche Beschränkungen etc.) Die Rechte Seite des Fensters enthält den Streetview. Du kannst die Ansicht in alle Richtungen verschieben mit der Maus, oder mit der Steuerung oben links im Streetview-Fenster. Zoomen kannst Du über den Regler oder mit dem Mausrad. Um die Position der Ansicht zu verschieben, kannst Du auf die Pfeile unterhalb der Bildmitte klicken oder Dich per Mausklick fortbewegen. Du kannst auch die Linse auf der Karte verschieben, mit dem kleinen weißen Punkt darunter. [[Image:Streetview-situation.png|700px]] Wenn Du zu viel auf einmal aktivierst, wirst Du feststellen, dass der bearbeitbare Bereich auf der Karte immer kleiner wird. Z.B. eine Aktualisierungsanfrage mit dem Fenster für Kommentare. Denke an die Tastaturkürzel, denn der Zoom-Regler der Karte ist dann verdeckt und somit kannst Du nur noch mit den Tastaturkürzeln Zoomen. Um den Streetview zu beenden, klicke auf das X in der oberen, rechten Ecke des Streetview-Fensters. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Der Editor-Chat== Wird demnächst erstellt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ebenen-Auswahl== Auf der rechten Seite der Karte findest Du dieses Symbol: [[Image:Layers-Auswahl.png]] Wenn Du mit der Maus darüber fährst, zeigt es Dir an, welche Ebenen aktuell ausgewählt sind. Die Ebenen mit den vier Punkten vor dem Namen, kannst Du in der Auswahl beliebig anordnen. [[WME_Schnellstart-Anleitung#Tastaturk.C3.BCrzel|'''Tastaturkürzel''']]. [[File:Ebenen.png]] Hier ein paar Informationen dazu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Die Luftaufnahmen=== [[Image:Aerial_skinny.png|260px]] Tastaturkürzel: '''Shift+b''' Waze benutzt Luftaufnahmen von Google (oder VirtualEarth). </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Städte=== [[Image:cities_skinny.png|260px]] Tastaturkürzel: '''Shift+c''' Diese Ebene zeigt die Grenzen der Städte verschiedenfarbig an in Form von Polygonen. Je nachdem, wie die Segmente benannt wurden. Dies ist hilfreich, um falsch benannte Segmente zu identifizieren. Manchmal können die Grenzen überlappen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Straßen=== [[Image:Road_segments_skinny.png|260px]] Tastaturkürzel: '''Shift+r''' In der Ebene sind die Straßen, Gassen, Autobahnen etc., aus denen sich die fahrbare Karte des Systems in Waze zusammensetzt. Je nach Zoom-Stufe sind einige Straßen nicht sichtbar, damit die Karte nicht zu unübersichtlich dargestellt wird. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===GPS-Punkte=== [[Image:Gps_tracks_straight_skinny.png|260px]] Tastaturkürzel: '''Shift+g''' Diese Ebene zeigt die GPS-Punkte der Benutzer an, die mit der Waze-App herumgefahren sind. Waze zeichnet die GPS-Koordinaten der Fahrer auf und wandelt sie in farbige Pfeile um, diese sind dann in der Karte sichtbar. Diese Ebene ist sehr hilfreich, um Straßen auf der Karte an richtiger Stelle zu platzieren, wenn z.B. keine Luftbilder vorhanden sind. Die Pfeile haben unterschiedliche Farben in jeder Fahrtrichtung. Das macht es einfacher, fehlerhafte GPS-Spuren zu lokalisieren oder Straßen auf der Karte zu finden, die nicht dem tatsächlichen Straßenverlauf folgen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Area-Manager=== Zeigt die Area-Manager im ausgewählten Ausschnitt an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Orientierungspunkte=== [[Image:Landmarks_skinny.png|260px]] Tastaturkürzel: '''Shift+l''' Orientierungspunkte sind auch unter Landmarks oder POI's (Points of Interest) bekannt. Diese können für nahezu alles verwendet werden: Tankstellen, Parks, Flüsse. Friedhöfe etc. Mehr Informationen zu den Orientierungspunkten findest Du [[Erstellen und bearbeiten von Landmarks|hier]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Blitzer=== [[Image:Speed_cam_enabled.png]] [[Image:Red-light_cam_enabled.png]] [[File:Fakeblitzer.png]] Tastaturkürzel: '''Shift+s''' In dieser Ebene kann man Geschwindigkeits-, Rotlicht- und Fake-Blitzer anzeigen lassen. Wer mit Waze durch die Straßen fährt, kann über die Anwendung Blitzer melden. Die Blitzer müssen im Karteneditor bearbeitet und bestätigt werden. Vorher erscheinen sie nicht auf der Anwendung. Bestätigte Blitzer warnen optisch und akustisch während der Fahrt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ====Geschwindigkeits-Blitzer==== Diese Blitzer sind fest montierte Blitzer im Straßenverkehr und blitzen die Fahrer bei Geschwindigkeitsübertretung. Die Blitzer in Waze blitzen in die Fahrtrichtung, das heißt: Will man gewarnt werden, muss man den roten Punkt im Karteneditor der Fahrtrichtung entlang ausrichten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ====Rotlicht-Blitzer==== Diese Blitzer sind fest montierte Rotlicht-Blitzer. Diese blitzen, wenn ein Rotlicht missachtet wird. Rotlicht-Blitzer in Waze warnen nur aus einer Richtung, das heißt: Will man von 4 Seiten her gewarnt werden, müssen 4 Blitzer positioniert werden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ====Fake-Blitzer==== Fake-Blitzer sind Attrappen, die nur so aussehen wie ein richtiger Blitzer und sollen den Fahrer zur Vorsicht bewegen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Kartenfehler=== [[Image:Problem_pin_open-low.gif|left]][[Image:Problem_pin_open-med.gif]] [[Image:Problem_pin_open-high.gif]] Tastaturkürzel: '''Shift+p''' <br> Der Waze-Server analysiert laufend die GPS-Daten, um Fehler zu erkennen. Diese werden dann über die Ebene Kartenfehler sichtbar. Sie sollen den Benutzer, der die Karte bearbeitet darauf hinweisen, dass die Karte Fehler aufweist, die es zu bearbeiten gilt. Typische Kartenfehler sind: Fehlende Straßen, falsche Abbiegungen, falsche Einbahnstraßen oder fehlende Verbindungen zwischen Segmenten. Für Informationen, lies [[WME Map Problems]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Aktualisierungsanfragen=== [[Image:Request_pin_open-low.gif|left]][[Image:Request_pin_open-med.gif]] [[Image:Request_pin_open-high.gif]] Tastaturkürzel: '''Shift+u''' <br> Die Aktualisierungsanfragen werden von den Benutzern der Waze-App während der Fahrt oder auf der "Echtzeit-Karte" gemeldet. * Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei gefahren ist, zeigt die Ebene im Karteneditor hellgrün an. * Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei während der Navigation gefahren ist, zeigt die Ebene im Karteneditor lila an mit den Abbiege-Anweisungen, die der Benutzer dabei erhalten hat. * Für Informationen, lies [[WME Update Requests]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Meine Gebiete=== [[Image:Editable_area_skinny.png|260px]] Tastaturkürzel: '''Shift+e''' Wo Du die Karte bearbeiten kannst, hängt davon ab, wo Du mit der Waze-App gefahren bist. Die Rechte sind im Umkreis von 1 Meile bzw. 1,6 Kilometer um die befahrene Strecke vorhanden. Die Gebiete die Du bearbeiten kannst, zeigen sich im Karteneditor wie folgt: * Hell hinterlegt sind Gebiete, die Du mit Waze befahren hast. * Die farbigen Gebiete sind die, in denen Du Area-Manager bist. * Dunkle Gebiete kannst Du nicht bearbeiten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Permalink-Schaltfläche== [[Image:Permalink-neu.png]] Außerhalb der Karte unten rechts befindet sich die Permalink-Schaltfläche. Der Permalink ändert immer dann, wenn die Karte verschoben wird, Objekte ausgewählt oder deselektiert werden. Man beachte: Der Permalink wird nicht jedesmal automatisch neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn man eine Browser-Sitzung wiederherstellt inkl. Editor, wird der Browser die letzte Kartenposition des Permalinks anzeigen, den man zuvor generiert hat. Wenn man Permalink anklickt, speichert dieser alle Informationen für den ausgewählten Kartenausschnitt. Man kann ihn anklicken, um die Karte zu aktualisieren, mit einem Rechtsklick kopieren, mit anderen Benutzern im Forum teilen oder als Lesezeichen ablegen. Vor allem bei Fragen zur Karte wird der Permalink im Forum oft gebraucht. Denn er speichert auch ausgewählte Straßen, Kreuzungen und Landmarks, so zeigt er anderen Benutzern schnell, was gemeint ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Anzeige des Längen- und Breitengrades== [[Image:Koordinaten.png]] In der unteren rechten Ecke befindet sich die Anzeige des Längen- und Breitengrades. Sie zeigt den aktuellen Ort, wo der Mauszeiger gerade hinzeigt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Zoom-Skala== {| style="float:left; background: transparent;" width="400" | [[Image:Zoom-Skala.png|left]] |- |Unten rechts befindet sich die Anzeige der Zoom-Stufe. Die Werte in der Skala rechts entsprechen auch der [[#Zoom-Steuerung | Zoomstufe]], die Du in der URL des Browsers siehst (zoom=5). Änderst Du die Zoomstufe darin, verändert sich auch die Ansicht. |} {| style="float:right;" | [[Image:Stufenscala.png]] |} {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karteneditor Steuerung= * Bewege die Karte, indem Du sie mit der Maus umherziehst. * Mit den Pfeiltasten kannst Du die Karte in alle vier Richtungen verschieben. * Es gibt vier Möglichkeiten die Karte zu zoomen: # Über die Zoom-Steuerung am linken oberen Rand der Karte. Regler hoch oder runterziehen mit der Maus oder klicke auf die + oder - Buttons. # Ein Doppelklick auf der Karte zoomt die Karte um eine Stufe rein und zentriert den Ausschnitt an den Ort, wohin man geklickt hat. # Am Mausrad drehen. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. Auf dem Mac mit einem Trackpad oder ähnlichem, nach links und rechts ziehen bewirkt das selbe. # Die ''Shift'' Taste drücken und ein Rechteck auf der Karte Zeichnen. Die Karte zoomt den ausgewählten Auschnitt ein: [[Image:Shift_zoom.png|500px|center]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =WME Schnell-Start Anleitung= Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Um die besten Techniken zu kennen und anzuwenden, braucht ein bisschen Zeit. Aber es kann auch Spaß machen mit wachsender Erfahrung. Man kann Stolz sein darauf, die Anwendung mit ein paar einfachen Bearbeitungsschritten für alle Endbenutzer zu verbessern. Die Links später in dieser Anleitung sind sehr wichtig, um alles zu erlernen was es braucht. Für die einfache Bearbeitung gibt es hier die [[WME Schnellstart-Anleitung]] um sich schnell zurecht zu finden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Permalink= : [[Image:wme permalink highlight.jpg]] * Im Karteneditor ist der [[Glossar#Permalink|Permalink]] eine URL, die Dich direkt an einen spezifischen Punkt auf der Karte bringt. Er speichert Längen- und Breitengrad, Zoom Stufe und alle Sichtbaren Objekte die während der Bearbeitung aktiv sind auf der Karte (ausgewählt in den Ebenen). Um genau auf ein Problem hinzuweisen sollte das betreffende Objekt ausgewählt sein, dies wird nämlich auch gespeichert. * Nach dem Klick auf Permalink unten rechts im Karteneditor, findest Du die Adresse zum Link in der Adresszeile des Browsers. Diese kann kopiert und in Foren-Beiträgen oder Lesezeichen eingefügt werden. Dies funktioniert auch wenn Du Permalink mit der rechten Maustaste auswählt und die Adresse direkt kopierst. * Hinweis: Der Permalink wird nicht jedesmal neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn Du eine Browser Sitzung wiederherstellst inkl. Editor, wird der Browser die letzte Karten-Position des Permalinks anzeigen, den Du zuvor generiert hast. * Falls die Straßen nicht mit den Luftaufnahmen übereinstimmen oder eine ungewöhnliche Position aufweisen, kannst Du mit dem Permalink die Seite aktualisieren, was das Problem in der Regel löst. * Was andere Editoren im Permalink sehen können, hängt von den Rechten ab, die sie besitzen. Ein Editor kann Aktualisierungsanfragen (Update Requests) oder Kartenfehler (Map Problems) nur in seinem bearbeitbaren Gebiet sehen. Also die lokalen Editoren, Area-Manager oder Country-Manager der betreffenden Gebiete oder Länder. Wenn Du ein breiteres Publikum betreffend eines Problems erreichen willst, musst Du ein Bildschirmfoto posten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Permalink in der Echtzeitkarte= Willst Du einen Permalink in der Echtzeitkarte generieren, musst Du auf die Permalink-Schaltfläche in der unteren, rechten Ecke der Karte klicken. Routen werden dabei auch gespeichert. *[[Image:PermalinkLiveMap.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tastaturkürzel= Der Einfachheit halber sind alle Kürzel im [[WME_Schnellstart-Anleitung#Tatstaturk.C3.BCrzel|WME Schnellstart-Anleitung]] an einem Ort zusammengefasst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karten Aktualisierung= Alles was bearbeitet wurde mit dem Karteneditor, wird früher oder später auf der Live Map und in der Waze-App zu sehen sein. Das Ziel von Waze ist es, alle Daten innerhalb von 24 Stunden zu aktualisieren. Dies kann auch mal länger dauern, schau Dir deshalb auch die Seite [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] an. * Die Aktualisierungen und sonstige Ereignisse, werden auch auf der [http://status.waze.com/ Status-Seite] von Waze publiziert. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Einsatz von externen Quellen (wie Google Imagery)= Die Verwendung von beliebigen externen, urheberrechtlich geschützten Informationsquellen, um Informationen in die Datenbank oder die Waze-Karten einzupflegen, ist nicht erlaubt. Externe urheberrechtlich geschützte Informationsquellen beinhaltet alle Online- oder gedruckten Karteninformationen, die nicht von Waze durch die Schnittstelle des Karteneditors bereitgestellt werden. Mit der Akquisition von Waze durch Google, Inc., wurde der Karteneditor von Waze mit Luftaufnahmen von Google und dem Streetview aktualisiert. Diese gelten als interne Quellen und dürfen daher verwendet werden, um Karteninformationen zur Waze-Karte hinzuzufügen. Googles Nutzungsbedingungen binden die Nutzung ihrer Karteninformationen an spezifische Bedingungen und Waze besitzt nur die ordnungsgemäße Lizenz, das was im Karteneditor zu sehen ist auch zu nutzen, aber sonst nichts anderes von Google. Die Verwendung von externen, urheberrechtlich geschützten Quellen gefährden die Karten und Waze wird dadurch gezwungen, alle Änderungen zu löschen und den Urzustand der Karte wieder herzustellen. Dies betrifft alle Änderung des betreffenden Benutzers auf der ganzen Karte! Wenn Du Karten in der Form erstellst, sieht sich Waze leider gezwungen, Deine ganze Arbeit von der Karte zu löschen. So ist es bereits in Chile und anderen Südamerikanischen Ländern passiert aufgrund der Lizenzprobleme. (kein Fehler seitens Waze!) Du darfst gerne mit lokalen Anbietern oder Behörden kommunizieren um allf. Luftaufnahmen oder Informationen zu erhalten, die verwendet werden dürfen. Du musst allerdings dabei klar erwähnen, dass Du nicht für Waze arbeitest oder in Auftrag von Waze handelst. Aber als interessierter Bürger kannst Du natürlich mit den lokalen Behörden sprechen, um die Vorteile für die Allgemeinheit zu erklären, z.B Luftaufnahmen als öffentliches Gut frei zur Verfügung zu stellen. Bei Fragen oder wenn Du nicht sicher bist, kommuniziere unbedingt mit dem Waze-Support. Beachte, dass externe Urheberrechtsinformationen keine Informationsquellen beinhalten, die von Waze durch die internen Werkzeuge des Karteneditors oder der Waze-App zur Verfügung gestellt werden. Auch alle Informationen, die selbstständig von einem Benutzer entwickelt wurden und physisch an einer Stelle abrufbar sind, werden akzeptiert, um damit die Karte zu bearbeiten, solange es nicht urheberrechtlich geschützt zur Verfügung gestellt wurde. Du darfst mit dem Support reden, wenn Du eine Quelle benutzen möchtest und nicht sicher bist, ob Du sie auch verwenden darfst. Waze wird die Quelle prüfen und Dir mitteilen, ob Du sie verwenden darfst oder nicht. Wenn nicht klar ist, ob eine Verwendung Legal ist, gelten die nachfolgenden Verbote. '''Folgendes ist Verboten:''' *Nachschauen ob der Straßenname korrekt ist. *Straßennamen von anderen Karten abtippen. *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren (manuell). *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren mit einem Skript. '''Es ist sehr einfach:''' *Verwende den Karteneditor mit den Möglichkeiten, die innerhalb Waze angeboten werden. *Vermeide alles andere, sofern nicht geprüft und bestätigt von Waze. Darum zeigt Waze im Karteneditor nur die Streetview Bilder ohne zusätzliche Daten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 0fb69722594825cbfd479d133767aee7be3a2109 11909 11908 2017-04-08T21:00:06Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Die Straßenkarten= Die Waze Basis-Karte (Base Map) wurde in vielen Ländern, durch den Import von öffentlich verfügbaren Straßendaten in das System generiert. Diese Daten sind ziemlich genau in der Geometrie, sie können aber etwas Bearbeitung gebrauchen. Außerdem nicht enthalten sind: Zulässige Fahrtrichtungen, Abbiegeregeln, Unterscheidung zwischen befahrbaren und nicht befahrbaren Straßen, wie Eisenbahnen und Fußwege. In den importierten Karten wird auch nicht unterschieden zwischen Brücke oder Kreuzung. Standardmässig ist alles mit einer Kreuzung verbunden und braucht daher definitiv Bearbeitung und Pflege. Hier kommen zwei wichtige Aspekte ins Spiel: # Der Karteneditor für die Benutzer, welche die Karten ihrer Stadtteile, Städte oder anderer Orte bearbeiten, mit denen sie vertraut sind. # Das Sammeln von GPS-Daten der App-Benutzer um die Karte automatisiert zu modifizieren, Fahrtrichtungen und Abbiegungen an Kreuzungen zu ermitteln. In einigen Ländern sind keine Basis-Daten verfügbar für die Straßenkarte, die Karten in diesen Ländern müssen von Grund auf neu aufgebaut werden. Sie werden durch die Benutzer im Karteneditor erstellt. Dabei werden aufgezeichnete Straßen der Waze-App und im Karteneditor neugezeichnete Straßen verwendet. Zur Hilfe stehen im Karteneditor gesammelte GPS-Punkte und vielerorts Luftaufnahmen zur Verfügung. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Karteneditor= * Der Standard-Editor für Waze heißt "Waze Map-Editor" oder kurz "WME". * Der WME wurde mit dem internen Codenamen "Papyrus" versehen. * Wenn Du an der Karte arbeitest, bitte [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] beachten. * Mit dem Karteneditor kannst Du alles in einer vordefinierten Gegend bearbeiten. Diese richtet sich nach den [[Rechte_zum_Bearbeiten_der_Karte#Rechte_basierend_auf_Fahrten|Rechten]], die Du bei Deiner Fahrt erwirbst oder der Funktion, die Dir zugesprochen wurde. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Simulation== Du kannst den Karteneditor auch einfach ausprobieren, dafür wurde eine Simulation geschaffen. Deine Änderungen werden nicht übernommen und auch nicht auf der Karte erscheinen. Probiers und schau Dir auch das Video an! Wenn Du den Karteneditor das erste Mal startest, siehst Du folgendes: [[Image:Playmode1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Im Karteneditor anmelden== * Unterstützt wird offiziell der Chrome Browser. Der Karteneditor läuft aber auch mit Firefox oder Safari. '''Die Anmeldung:''' * Anmeldung im Waze-Konto mit dem Benutzernamen auf der Waze-Homepage, der Link zur Anmeldung befindet sich oben rechts auf der Seite https://www.waze.com/de/ * Auswahl des Links "Echtzeit-Karte" in der Haupt-Navigationsleiste * Auswahl des Links "Karteneditor" in der Suchleiste * Du kannst Dich auch direkt im Karteneditor anmelden mit Benutzername und Passwort: https://www.waze.com/de/editor/ * Du kannst den Link auch als Lesezeichen ablegen *Auf der Seite [[WME Tipps und Tricks]] gibt es Informationen dazu. Wenn Du Dich korrekt angemeldet hast, siehst Du folgendes: [[Image:Login1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Start-Position des Karteneditors== Um den Karteneditor an einer bestimmten Stelle zu starten: # Wähle den gewünschten Kartenausschnitt aus. # Klick auf Permalink # Kopiere die URL in der Adressleiste deines Browsers in die Lesezeichen. * So kannst Du ein Gebiet deiner Wahl als Startpunkt des Karteneditors bestimmen. Immer wenn Du den Karteneditor über das Lesezeichen öffnest, wird er Dich genau an diese Stelle bringen. * Der Karteneditor öffnet sich in der Regel an der Stelle, wo Du als letztes gearbeitet hast. Es sei denn Du löschst den Cache deines Browsers. Dann ist der Startpunkt London. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Auswählen der Sprache== Die Sprachauswahl des Karteneditors befindet sich in der oberen, rechten Ecke der Haupt-Navigationsleiste [[File:Sprachauswahl.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Oberfläche und Steuerelemente= ==Aussehen des Karteneditors== Es gibt drei Hauptelemente im Waze Map-Editor: # Die Werkzeugleiste # Die Reiter # Der Anzeigebereich der Karte [[File:Anzeige4.png|700px]] Zuoberst ist die Werkzeugleiste mit einem Suchfeld und Buttons für: Hinzufügen, Speichern, Rückgängig, Wiederholen und Löschen.<br> Auf der linken Seite befinden sich die Reiter. Wenn kein Segment ausgewählt ist, zeigen die Reiter: * '''Ich''' Deinen Benutzernamen, das Total Deiner Punkte, Deine Rechte und einen Link zum Map Editing Video. * '''Fahrten''' Wo Du mit Waze gefahren bist. * '''Gebiete''' Wo Du überall die Karte bearbeiten darfst. Wenn ein Segment ausgewählt ist, zeigen die Reiter: * '''Eigenschaften''' Alle Eigenschaften an, die Du bearbeiten kannst. Straßentyp, Richtung, Level, Mautstraße oder Straßen sperren (Lock) * '''Bearbeiten''' zeigt alle anderen Eigenschaften, wie: Land, Stadt, Straße oder Alternative Straßennamen. *'''Gesamte Straße auswählen''' erlaubt das Auswählen eines gesamten Straßenzugs. *'''Hausnummern bearbeiten''' erlaubt das Bearbeiten von Hausnummern für ein ausgewähltes Segment. Dies ist nur für ein einziges Segment möglich. Oben links unterhalb der Werkzeugleiste befindet sich: * Die Anzeige des aktuellen Orts. Auf der rechten Seite unterhalb der Werkzeugleiste: * Der Lade-Indikator (Karte lädt, Speichern etc.) und die Ebenen-Auswahl. Am unteren Rand des Hauptfensters befindet sich: * In der linken Ecke die Skala des Zoom-Stufen. * In der rechten Ecke die Permalink-Schaltfläche und die Anzeige des Längen- und Breitengrads der aktuellen Maus-Zeiger-Position. Auf der linken Seite unterhalb der Reiter befindet sich eine Schaltfläche mit Links zum Wiki, Forum, Status-Seite und zu den Tastaturkürzeln des Karteneditors.<br> [[File:EditorLinks.png]] Der Anzeigebereich der Karte, welcher die größte Fläche einnimmt, bietet die Möglichkeit zur Anzeige der Luftaufnahmen, Städte, Straßen, Kreuzungen, Orientierungspunkte, Blitzer, GPS-Punkte, Kartenfehler und der Gebiete, die man bearbeiten darf. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Werkzeugleiste== [[Image:WME-Werkzeugleiste.png|700px]] ===Das Suchfeld=== Im Suchfeld kann man Adressen, Städte, Staaten, Länder, Orientierungspunkte oder eine Kombination derer eingeben. Nach Betätigen der Eingabe-Taste oder klicken auf den Such-Button, wird entweder eine Auswahl angezeigt oder nur der gesuchte Ort. Beispiel: Suche nach "Blumenstraße, München" Wird dich an die gewünschte Adresse bringen und setzt einen Marker auf die Karte. [[Image:Suchfeld1.png|700px]] Eine Suche nach "Blumenstraße", zeigt einige Ergebnisse an. [[Image:Suchfeld2.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Hinzufügen=== [[Image:Button-hinzufügen.png|left]] Tastaturkürzel: '''i''', '''o''', '''u''', '''g''' oder '''p''' Der Hinzufügen-Button muss nur mit der Maus berührt werden, und es öffnet sich ein Menü mit den Aktionen. Von hier aus kannst Du Straßen, Kreisverkehre oder Orientierungspunkte etc. hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Speichern=== [[Image:Speichern1.png |left]] [[Image:Speichern2.png]] [[Image:Speichern3.png]] Tatstaturkürzel: '''Ctrl+s''' <br> Der Speichern-Button speichert alle aktuellen Bearbeitungsschritte. Der Button besitzt einen Zähler. 0-9 Bearbeitungsschritte werden in schwarzen Ziffern angezeigt und ab 10 Bearbeitungsschritten erscheinen die Ziffern rot. Wenn es beim Speichern einen Fehler gibt, erscheint ein Fenster mit einer Fehlermeldung, die das Problem normalerweise beschreibt. Der Map-Editor versucht die Stelle auf der Karte anzuzeigen, wo der Fehler liegt und zeigt den Fehler in Form eines hellen Kreises an. Sobald der Speichern-Button angeklickt wird, ist es nicht mehr möglich etwas rückgängig zu machen! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Rückgängig=== [[Image:Button-rueckgaengig.png|left]] Tastaturkürzel: '''Ctrl+Z''' Der Rückgängig-Button macht Schrittweise die Bearbeitungsschritte rückgängig, die '''noch nicht gespeichert''' wurden. <span style="color:red;">Wurde bereits gespeichert, ist es nicht mehr möglich etwas rückgängig zu machen, das man zuvor bearbeitet hat!</span> Ein Bearbeitungsschritt kann das Löschen einer Kreuzung sein, die Benennung einer Straße oder sonstigem. Wenn Du aber 10 Segmente auswählst und gleichzeitig bearbeitest um sie z.B. von "Unknown" auf 2spurig umzustellen, dann gilt dies als ein Bearbeitungsschritt, wenn Du den Rückgängig-Button drückst. Alle 10 Segmente werden dann rückgängig gemacht! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Wiederholen=== [[Image:Button-wiederholen.png|left]] Tastaturkürzel: '''Ctrl+Shift+Z''' Der Wiederholen-Button wiederholt alles, was der Rückgängig-Button zuvor rückgängig gemacht hat. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Löschen=== [[Image:Button-loeschen.png|left]] Tastaturkürzel: '''Delete (Del)''' Der Löschen-Button löscht alles was ausgewählt ist. Sind mehrere Segmente ausgewählt, muss man dies auf einem Popup bestätigen und danach kann gespeichert werden. Das einzige, was im Moment in Mehrfach-Auswahl gelöscht werden kann sind Straßen-Segmente. Der Rückgängig-Button kann auch bereits zur Löschung ausgewählte Objekte wiederherstellen, '''solange nicht gespeichert''' wurde nach dem Löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Reiter== [[File:Hallo.png]] Zuoberst grüßt man dich mit deinem Benutzernamen und zeigt dir das Total deiner Punkte an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Ich=== [[Image:Wazer-rechte.png]] Der Ich-Reiter zeigt einen Wazer mit gelbem Bauhelm, und die entsprechenden Rechte. Sie werden in orangfarbenen Pylonen dargestellt. Weiteres dazu [[Rechte zum Bearbeiten der Karte|hier]]. Darunter wird angezeigt, welche Rechte Du besitzt und das Total Deiner Punkte. Unterhalb der Benutzerinformationen befindet sich diese Schaltfläche: [[File:Benutzer Video.png]] Sie öffnet ein Interface, das 7 Videos über Waze auf Youtube enthält. Diese Videos sind auf Englisch und heißen: # Einführung # Bevor Du beginnst # Erste Schritte # Grundbegriffe # Grundlagen # Kartenfehler # Beispiele Diese animierte Anleitung ist ein guter Weg, um einen Überblick über das System und einige der Prozesse zu bekommen. Diese Videos sind nur eine Einführung. In den Dokumentationen und den [[Main_Page|Waze-Wikis]] sind die meisten Details über den Karteneditor zu finden. Auch wenn es um Richtlinien für Standards und länderspezifische Eigenheiten geht, sind diese unerlässlich. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Fahrten=== Unter "Fahrten" siehst Du die Strecken, die Du mit Waze gefahren bist. Wenn Du einen Eintrag auswählst, zoomt die Karte dahin und zeigt die Strecke innerhalb der Karte an. Oben auf der Karte wird ein Fenster angezeigt, das Dir zeigt, welche Strecke Du gefahren bist. Routen die länger als 20 Meilen/32 Kilometer sind, zeigt der Editor nicht innerhalb der Karte an. Du kannst dann anhand der gefahrenen Strecke eine Straße auf die Karte zeichnen, wenn Du "Straße erstellen" anklickst. Die Straßen, die Du erstellen kannst, zeigt der Streckenverlauf rot an. Erstelle keine Segmente über bereits bestehende Straßen. Schau Dir zuerst die Karte an! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Gebiete=== Diese Liste zeigt definierte Gebiete an, in denen Du arbeiten kannst. Entweder die Gebiete, die Du befahren hast oder die Gebiete in denen Du Area- oder Country-Manager bist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Segmente== [[File:Reiteranzeige.png|right]] [[File:Ausgewaehlt editmodus.png|right]] '''Einzelnes Segment ausgewählt:'''<br> Im oberen Teil werden der Name des Segments und die "Alternativen Straßennamen" angezeigt. Darunter der Bearbeiten-Button. Im unteren Teil wird Straßentyp, Richtung, Ebene und Stufe der Sperre angezeigt. '''Bei Mehrfach-Auswahl:'''<br> Der obere Bereich zeigt an, wie viele Segmente ausgewählt sind. Das Beispiel rechts zeigt, wie die Situation aussieht, wenn 2 Segmente ausgewählt sind im "Bearbeiten-Modus". '''Eigenschaften bearbeiten:'''<br> Wenn Du auf Bearbeiten klickst oder das Tastaturkürzel '''"e"''' drückst, wechselt die Ansicht in den Bearbeiten-Modus und zeigt alle wichtigen Informationen an. Es ermöglicht Dir alle Eigenschaften wie: Landes-, Stadt- und Straßennamen zu ändern. Das Feld für Bundesländer/Kantone resp. Staaten ist im Moment noch den USA vorbehalten. Auch alternative Straßennamen kannst Du bearbeiten. Dies ist dann interessant, wenn die Straße einen lokalen Namen besitzt, der nicht im Hauptfeld des Segments Platz hat, oder nicht offiziell gebräuchlich ist. Beispiel: Die A1 in Österreich hat im alternativen Namen die Bezeichnung "West Autobahn" Oder das Beispiel, das im Screenshot zu sehen ist.<br> '''Das Stadt-Feld des alternativen Namens muss den selben Namen, wie das Stadt-Feld des Segments besitzen.''' <br style="clear: both" /> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Orientierungspunkte== {| border="0" cellpadding="2" style="background:none;" |- style="vertical-align:top;" | Wenn Du eine Orientierungspunkt auswählst, kannst Du ihn benennen, einen Orientierungspunkt-Typ vergeben und den Orientierungspunkt mit einer Sperre versehen. Die Sperre hindert Editoren mit niedrigeren Stufen (Rechte) den Orientierungspunkt zu verändern: | | Darunter befinden sich die Adressdetails. ''Klick'' auf '''Bearbeiten''' und ändere die Details, ''klick'' auf '''Übernehmen''', wenn Du alles eingegeben hast: |- style="vertical-align:top;" | [[File:Orientierungspunktausgewaehlt.png]] | | [[File:Orientierungspunktausgewaehltadressdetails.png]] Wird eine korrekte Adresse eingegeben, ermöglichen wir damit Waze, die interne Suche für die Orientierungspunkte zu verwenden und nicht externe Anbieter. |} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Anzeigebereich der Karte= Alle ausgewählten Ebenen sind im Anzeigebereich der Karte zu sehen. Der Anzeigebereich der Karte nimmt den Hauptteil des Browser-Fensters ein. Jedes Objekt, das angezeigt wird ist auswählbar und kann bearbeitet werden. Dies hängt von den Rechten ab, die Du im ausgewählten Kartenausschnitt besitzt. Wähle eine Straße aus und verändere ihre Geometrie. Wähle einen Orientierungspunkt aus und gebe ihm einen Namen. Füge eine Straße hinzu, wo eine sein sollte oder lösche Straßen, die nicht mehr zu sehen sein sollen. Es gibt sieben Hauptbestandteile in den Ecken des Anzeigebereichs auf der Karte: # Die Infoleiste # Die Zoom-Steuerung inkl. Streetview # Die Schaltfläche für den Chat # Die Ebenen-Auswahl # Die Permalink-Schaltfläche # Die Anzeige des Längen- und Breitengrades # Die Zoom-Skala </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Info Leiste== [[File:Infoleiste.png|700px]] Unter dem Suchfeld befindet sich die Info-Leiste. * Links die Stadt und das Land des aktuellen Kartenausschnitts. * Rechts befindet sich eine Box, die nur erscheint, wenn etwas geladen wird. Karte lädt, Speichern, Straßen laden etc. Daneben die Ebenen-Auswahl. Probleme beim Speichern können hauptsächlich beim Verbinden an Kreuzungen und Geometrieänderungen entstehen. Deshalb arbeite sorgfältig, und Du ersparst dir Mehraufwand. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Zoom-Steuerung== [[Image:Zoomregler.png|left]] Tastaturkürzel: '''Shift+UpArrow''', Tastaturkürzel: '''Shift+DownArrow''' In der oberen linken Ecke befindet sich die Zoom-Skala, sie besitzt 10 Stufen. Die Steuerung der Skala + und - kann benutzt werden, um die Karte zu vergrößern oder zu verkleinern. Dies funktioniert auch, wenn der Regler verschoben wird, oder am einfachsten, wenn man am Mausrad dreht. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Streetview== [[Image:Streetview.png]] Direkt unter der Zoom-Steuerung befindet sich der Streetview. Ziehe die blaue Linse auf die Straße, die Du im Streetview anschauen möchtest. Der Streeview ist nicht überall vorhanden, er hängt davon ab, was uns Google zur Verfügung stellt. [[Image:Streetview-nicht-vorhanden.png|left]] Wo kein Streetview verfügbar ist, bleibt die Linse beim Ziehen über der Karte rot. <br style="clear: both" /> [[Image:Streetview-vorhanden.png|left]] Wo der Streetview verfügbar ist, färbt sich die Linse beim Ziehen über der Karte blau, Du kannst die Linse loslassen und die Straße im Streetview anschauen. <br style="clear: both" /> Wenn Du die Linse losgelassen hast, enthält sie einen Pfeil, der in die Richtung des Streetviews zeigt. [[Image:Wme streetview directional arrow.gif]] Während des Streetviews sind alle anderen Operationen möglich (Segment-Eigenschaften, Kartenfehler und Aktualisierungsanfragen, Hausnummern, zeitliche Beschränkungen etc.) Die Rechte Seite des Fensters enthält den Streetview. Du kannst die Ansicht in alle Richtungen verschieben mit der Maus, oder mit der Steuerung oben links im Streetview-Fenster. Zoomen kannst Du über den Regler oder mit dem Mausrad. Um die Position der Ansicht zu verschieben, kannst Du auf die Pfeile unterhalb der Bildmitte klicken oder Dich per Mausklick fortbewegen. Du kannst auch die Linse auf der Karte verschieben, mit dem kleinen weißen Punkt darunter. [[Image:Streetview-situation.png|700px]] Wenn Du zu viel auf einmal aktivierst, wirst Du feststellen, dass der bearbeitbare Bereich auf der Karte immer kleiner wird. Z.B. eine Aktualisierungsanfrage mit dem Fenster für Kommentare. Denke an die Tastaturkürzel, denn der Zoom-Regler der Karte ist dann verdeckt und somit kannst Du nur noch mit den Tastaturkürzeln Zoomen. Um den Streetview zu beenden, klicke auf das X in der oberen, rechten Ecke des Streetview-Fensters. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Der Editor-Chat== Wird demnächst erstellt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ebenen-Auswahl== Auf der rechten Seite der Karte findest Du dieses Symbol: [[Image:Layers-Auswahl.png]] Wenn Du mit der Maus darüber fährst, zeigt es Dir an, welche Ebenen aktuell ausgewählt sind. Die Ebenen mit den vier Punkten vor dem Namen, kannst Du in der Auswahl beliebig anordnen. [[WME_Schnellstart-Anleitung#Tastaturk.C3.BCrzel|'''Tastaturkürzel''']]. [[File:Ebenen.png]] Hier ein paar Informationen dazu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Die Luftaufnahmen=== [[Image:Aerial_skinny.png|260px]] Tastaturkürzel: '''Shift+b''' Waze benutzt Luftaufnahmen von Google (oder VirtualEarth). </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Städte=== [[Image:cities_skinny.png|260px]] Tastaturkürzel: '''Shift+c''' Diese Ebene zeigt die Grenzen der Städte verschiedenfarbig an in Form von Polygonen. Je nachdem, wie die Segmente benannt wurden. Dies ist hilfreich, um falsch benannte Segmente zu identifizieren. Manchmal können die Grenzen überlappen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Straßen=== [[Image:Road_segments_skinny.png|260px]] Tastaturkürzel: '''Shift+r''' In der Ebene sind die Straßen, Gassen, Autobahnen etc., aus denen sich die fahrbare Karte des Systems in Waze zusammensetzt. Je nach Zoom-Stufe sind einige Straßen nicht sichtbar, damit die Karte nicht zu unübersichtlich dargestellt wird. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===GPS-Punkte=== [[Image:Gps_tracks_straight_skinny.png|260px]] Tastaturkürzel: '''Shift+g''' Diese Ebene zeigt die GPS-Punkte der Benutzer an, die mit der Waze-App herumgefahren sind. Waze zeichnet die GPS-Koordinaten der Fahrer auf und wandelt sie in farbige Pfeile um, diese sind dann in der Karte sichtbar. Diese Ebene ist sehr hilfreich, um Straßen auf der Karte an richtiger Stelle zu platzieren, wenn z.B. keine Luftbilder vorhanden sind. Die Pfeile haben unterschiedliche Farben in jeder Fahrtrichtung. Das macht es einfacher, fehlerhafte GPS-Spuren zu lokalisieren oder Straßen auf der Karte zu finden, die nicht dem tatsächlichen Straßenverlauf folgen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Area-Manager=== Zeigt die Area-Manager im ausgewählten Ausschnitt an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Orientierungspunkte=== [[Image:Landmarks_skinny.png|260px]] Tastaturkürzel: '''Shift+l''' Orientierungspunkte sind auch unter Landmarks oder POI's (Points of Interest) bekannt. Diese können für nahezu alles verwendet werden: Tankstellen, Parks, Flüsse. Friedhöfe etc. Mehr Informationen zu den Orientierungspunkten findest Du [[Erstellen und bearbeiten von Landmarks|hier]]. </noinclude></noinclude> </noinclude> </noinclude> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Kartenfehler=== [[Image:Problem_pin_open-low.gif|left]][[Image:Problem_pin_open-med.gif]] [[Image:Problem_pin_open-high.gif]] Tastaturkürzel: '''Shift+p''' <br> Der Waze-Server analysiert laufend die GPS-Daten, um Fehler zu erkennen. Diese werden dann über die Ebene Kartenfehler sichtbar. Sie sollen den Benutzer, der die Karte bearbeitet darauf hinweisen, dass die Karte Fehler aufweist, die es zu bearbeiten gilt. Typische Kartenfehler sind: Fehlende Straßen, falsche Abbiegungen, falsche Einbahnstraßen oder fehlende Verbindungen zwischen Segmenten. Für Informationen, lies [[WME Map Problems]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Aktualisierungsanfragen=== [[Image:Request_pin_open-low.gif|left]][[Image:Request_pin_open-med.gif]] [[Image:Request_pin_open-high.gif]] Tastaturkürzel: '''Shift+u''' <br> Die Aktualisierungsanfragen werden von den Benutzern der Waze-App während der Fahrt oder auf der "Echtzeit-Karte" gemeldet. * Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei gefahren ist, zeigt die Ebene im Karteneditor hellgrün an. * Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei während der Navigation gefahren ist, zeigt die Ebene im Karteneditor lila an mit den Abbiege-Anweisungen, die der Benutzer dabei erhalten hat. * Für Informationen, lies [[WME Update Requests]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Meine Gebiete=== [[Image:Editable_area_skinny.png|260px]] Tastaturkürzel: '''Shift+e''' Wo Du die Karte bearbeiten kannst, hängt davon ab, wo Du mit der Waze-App gefahren bist. Die Rechte sind im Umkreis von 1 Meile bzw. 1,6 Kilometer um die befahrene Strecke vorhanden. Die Gebiete die Du bearbeiten kannst, zeigen sich im Karteneditor wie folgt: * Hell hinterlegt sind Gebiete, die Du mit Waze befahren hast. * Die farbigen Gebiete sind die, in denen Du Area-Manager bist. * Dunkle Gebiete kannst Du nicht bearbeiten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Permalink-Schaltfläche== [[Image:Permalink-neu.png]] Außerhalb der Karte unten rechts befindet sich die Permalink-Schaltfläche. Der Permalink ändert immer dann, wenn die Karte verschoben wird, Objekte ausgewählt oder deselektiert werden. Man beachte: Der Permalink wird nicht jedesmal automatisch neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn man eine Browser-Sitzung wiederherstellt inkl. Editor, wird der Browser die letzte Kartenposition des Permalinks anzeigen, den man zuvor generiert hat. Wenn man Permalink anklickt, speichert dieser alle Informationen für den ausgewählten Kartenausschnitt. Man kann ihn anklicken, um die Karte zu aktualisieren, mit einem Rechtsklick kopieren, mit anderen Benutzern im Forum teilen oder als Lesezeichen ablegen. Vor allem bei Fragen zur Karte wird der Permalink im Forum oft gebraucht. Denn er speichert auch ausgewählte Straßen, Kreuzungen und Landmarks, so zeigt er anderen Benutzern schnell, was gemeint ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Anzeige des Längen- und Breitengrades== [[Image:Koordinaten.png]] In der unteren rechten Ecke befindet sich die Anzeige des Längen- und Breitengrades. Sie zeigt den aktuellen Ort, wo der Mauszeiger gerade hinzeigt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Zoom-Skala== {| style="float:left; background: transparent;" width="400" | [[Image:Zoom-Skala.png|left]] |- |Unten rechts befindet sich die Anzeige der Zoom-Stufe. Die Werte in der Skala rechts entsprechen auch der [[#Zoom-Steuerung | Zoomstufe]], die Du in der URL des Browsers siehst (zoom=5). Änderst Du die Zoomstufe darin, verändert sich auch die Ansicht. |} {| style="float:right;" | [[Image:Stufenscala.png]] |} {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karteneditor Steuerung= * Bewege die Karte, indem Du sie mit der Maus umherziehst. * Mit den Pfeiltasten kannst Du die Karte in alle vier Richtungen verschieben. * Es gibt vier Möglichkeiten die Karte zu zoomen: # Über die Zoom-Steuerung am linken oberen Rand der Karte. Regler hoch oder runterziehen mit der Maus oder klicke auf die + oder - Buttons. # Ein Doppelklick auf der Karte zoomt die Karte um eine Stufe rein und zentriert den Ausschnitt an den Ort, wohin man geklickt hat. # Am Mausrad drehen. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. Auf dem Mac mit einem Trackpad oder ähnlichem, nach links und rechts ziehen bewirkt das selbe. # Die ''Shift'' Taste drücken und ein Rechteck auf der Karte Zeichnen. Die Karte zoomt den ausgewählten Auschnitt ein: [[Image:Shift_zoom.png|500px|center]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =WME Schnell-Start Anleitung= Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Um die besten Techniken zu kennen und anzuwenden, braucht ein bisschen Zeit. Aber es kann auch Spaß machen mit wachsender Erfahrung. Man kann Stolz sein darauf, die Anwendung mit ein paar einfachen Bearbeitungsschritten für alle Endbenutzer zu verbessern. Die Links später in dieser Anleitung sind sehr wichtig, um alles zu erlernen was es braucht. Für die einfache Bearbeitung gibt es hier die [[WME Schnellstart-Anleitung]] um sich schnell zurecht zu finden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Permalink= : [[Image:wme permalink highlight.jpg]] * Im Karteneditor ist der [[Glossar#Permalink|Permalink]] eine URL, die Dich direkt an einen spezifischen Punkt auf der Karte bringt. Er speichert Längen- und Breitengrad, Zoom Stufe und alle Sichtbaren Objekte die während der Bearbeitung aktiv sind auf der Karte (ausgewählt in den Ebenen). Um genau auf ein Problem hinzuweisen sollte das betreffende Objekt ausgewählt sein, dies wird nämlich auch gespeichert. * Nach dem Klick auf Permalink unten rechts im Karteneditor, findest Du die Adresse zum Link in der Adresszeile des Browsers. Diese kann kopiert und in Foren-Beiträgen oder Lesezeichen eingefügt werden. Dies funktioniert auch wenn Du Permalink mit der rechten Maustaste auswählt und die Adresse direkt kopierst. * Hinweis: Der Permalink wird nicht jedesmal neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn Du eine Browser Sitzung wiederherstellst inkl. Editor, wird der Browser die letzte Karten-Position des Permalinks anzeigen, den Du zuvor generiert hast. * Falls die Straßen nicht mit den Luftaufnahmen übereinstimmen oder eine ungewöhnliche Position aufweisen, kannst Du mit dem Permalink die Seite aktualisieren, was das Problem in der Regel löst. * Was andere Editoren im Permalink sehen können, hängt von den Rechten ab, die sie besitzen. Ein Editor kann Aktualisierungsanfragen (Update Requests) oder Kartenfehler (Map Problems) nur in seinem bearbeitbaren Gebiet sehen. Also die lokalen Editoren, Area-Manager oder Country-Manager der betreffenden Gebiete oder Länder. Wenn Du ein breiteres Publikum betreffend eines Problems erreichen willst, musst Du ein Bildschirmfoto posten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Permalink in der Echtzeitkarte= Willst Du einen Permalink in der Echtzeitkarte generieren, musst Du auf die Permalink-Schaltfläche in der unteren, rechten Ecke der Karte klicken. Routen werden dabei auch gespeichert. *[[Image:PermalinkLiveMap.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tastaturkürzel= Der Einfachheit halber sind alle Kürzel im [[WME_Schnellstart-Anleitung#Tatstaturk.C3.BCrzel|WME Schnellstart-Anleitung]] an einem Ort zusammengefasst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karten Aktualisierung= Alles was bearbeitet wurde mit dem Karteneditor, wird früher oder später auf der Live Map und in der Waze-App zu sehen sein. Das Ziel von Waze ist es, alle Daten innerhalb von 24 Stunden zu aktualisieren. Dies kann auch mal länger dauern, schau Dir deshalb auch die Seite [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] an. * Die Aktualisierungen und sonstige Ereignisse, werden auch auf der [http://status.waze.com/ Status-Seite] von Waze publiziert. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Einsatz von externen Quellen (wie Google Imagery)= Die Verwendung von beliebigen externen, urheberrechtlich geschützten Informationsquellen, um Informationen in die Datenbank oder die Waze-Karten einzupflegen, ist nicht erlaubt. Externe urheberrechtlich geschützte Informationsquellen beinhaltet alle Online- oder gedruckten Karteninformationen, die nicht von Waze durch die Schnittstelle des Karteneditors bereitgestellt werden. Mit der Akquisition von Waze durch Google, Inc., wurde der Karteneditor von Waze mit Luftaufnahmen von Google und dem Streetview aktualisiert. Diese gelten als interne Quellen und dürfen daher verwendet werden, um Karteninformationen zur Waze-Karte hinzuzufügen. Googles Nutzungsbedingungen binden die Nutzung ihrer Karteninformationen an spezifische Bedingungen und Waze besitzt nur die ordnungsgemäße Lizenz, das was im Karteneditor zu sehen ist auch zu nutzen, aber sonst nichts anderes von Google. Die Verwendung von externen, urheberrechtlich geschützten Quellen gefährden die Karten und Waze wird dadurch gezwungen, alle Änderungen zu löschen und den Urzustand der Karte wieder herzustellen. Dies betrifft alle Änderung des betreffenden Benutzers auf der ganzen Karte! Wenn Du Karten in der Form erstellst, sieht sich Waze leider gezwungen, Deine ganze Arbeit von der Karte zu löschen. So ist es bereits in Chile und anderen Südamerikanischen Ländern passiert aufgrund der Lizenzprobleme. (kein Fehler seitens Waze!) Du darfst gerne mit lokalen Anbietern oder Behörden kommunizieren um allf. Luftaufnahmen oder Informationen zu erhalten, die verwendet werden dürfen. Du musst allerdings dabei klar erwähnen, dass Du nicht für Waze arbeitest oder in Auftrag von Waze handelst. Aber als interessierter Bürger kannst Du natürlich mit den lokalen Behörden sprechen, um die Vorteile für die Allgemeinheit zu erklären, z.B Luftaufnahmen als öffentliches Gut frei zur Verfügung zu stellen. Bei Fragen oder wenn Du nicht sicher bist, kommuniziere unbedingt mit dem Waze-Support. Beachte, dass externe Urheberrechtsinformationen keine Informationsquellen beinhalten, die von Waze durch die internen Werkzeuge des Karteneditors oder der Waze-App zur Verfügung gestellt werden. Auch alle Informationen, die selbstständig von einem Benutzer entwickelt wurden und physisch an einer Stelle abrufbar sind, werden akzeptiert, um damit die Karte zu bearbeiten, solange es nicht urheberrechtlich geschützt zur Verfügung gestellt wurde. Du darfst mit dem Support reden, wenn Du eine Quelle benutzen möchtest und nicht sicher bist, ob Du sie auch verwenden darfst. Waze wird die Quelle prüfen und Dir mitteilen, ob Du sie verwenden darfst oder nicht. Wenn nicht klar ist, ob eine Verwendung Legal ist, gelten die nachfolgenden Verbote. '''Folgendes ist Verboten:''' *Nachschauen ob der Straßenname korrekt ist. *Straßennamen von anderen Karten abtippen. *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren (manuell). *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren mit einem Skript. '''Es ist sehr einfach:''' *Verwende den Karteneditor mit den Möglichkeiten, die innerhalb Waze angeboten werden. *Vermeide alles andere, sofern nicht geprüft und bestätigt von Waze. Darum zeigt Waze im Karteneditor nur die Streetview Bilder ohne zusätzliche Daten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] d5e24f799bc208f8254d50c6664f1002d25e7364 0 74 11912 2017-05-03T09:09:58Z Vince1612 23 Created new page wikitext text/x-wiki WORK IN PROGRESS * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] 3dc9fc947704c4ab8fe8324afe042a2557046611 11916 11912 2017-05-03T13:50:34Z Vince1612 23 wikitext text/x-wiki '''WORK IN PROGRESS - EN CONSTRUCTION''' * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] *** [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz Liste des villes de Suisse] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] 2cbb01eaa5a6c867c12e28b31d7e12d69e820863 11917 11916 2017-05-03T13:52:05Z Vince1612 23 wikitext text/x-wiki '''WORK IN PROGRESS - EN CONSTRUCTION''' * [[A propos de l'édition]] * [[Waze Map Editor (WME)]] ** [[Légende de la Carte Suisse]] ** [[Comment nommer les routes et les villes en Suisse]] ** [[Numéros de rue]] ** [[Guide des intersections]] ** [[Tout sur les Ronds-Points]] ** [[Station Essence]] * [[Points et Classement]] c1dcb96d40e05ab46d8f9f8a52b594fe96c7285a 11918 11917 2017-05-03T14:21:15Z Vince1612 23 Finalized changes wikitext text/x-wiki * Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. ** Quelques articles du wiki en français *** [[A propos de l'édition]] *** [[Légende de la Carte Suisse]] *** [[Comment nommer les routes et les villes en Suisse]] ** Pour tout ce qui est relatif à l'utilisation de WME sur l'aspect technique uniquement (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [[france:Accueil|Accueil]] ** Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] <u>'''IMPORTANT:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 2ba3d59924377572cea569706ee00bfcb42b02dd 11920 11918 2017-05-03T14:23:48Z Vince1612 23 paragraph change wikitext text/x-wiki * Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. ** Quelques articles du wiki en français *** [[A propos de l'édition]] *** [[Légende de la Carte Suisse]] *** [[Comment nommer les routes et les villes en Suisse]] ** Pour tout ce qui est relatif à l'utilisation de WME sur l'aspect technique uniquement (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [[france:Accueil|Accueil]] ** Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] <u>'''IMPORTANT:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' fbb04c825773b8a6bce6079d9ca8d683af902955 11921 11920 2017-05-03T14:24:21Z Vince1612 23 wikitext text/x-wiki * Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. ** Quelques articles du wiki en français *** [[A propos de l'édition]] *** [[Légende de la Carte Suisse]] *** [[Comment nommer les routes et les villes en Suisse]] ** Pour tout ce qui est relatif à l'utilisation de WME sur l'aspect technique uniquement (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [[france:Accueil|Accueil]] ** Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * <u>'''IMPORTANT:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 02b602f52ae9212d1a9eabe565c99bc1e930c772 11922 11921 2017-05-04T12:00:21Z Vince1612 23 wikitext text/x-wiki * Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. ** Quelques articles du wiki en français *** [[A propos de l'édition]] *** [[Légende de la Carte Suisse]] *** [[Comment nommer les routes et les villes en Suisse]] ** Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] ** Pour tout ce qui est relatif à l'utilisation de WME sur l'aspect technique uniquement (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [[france:Accueil|Accueil]] * <u>'''IMPORTANT:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 7e12606f23a7d9228f6b33815b0a63c7e7bae09c 0 15 11914 10839 2017-05-03T13:41:14Z Vince1612 23 /* Les serveurs */ wikitext text/x-wiki [[Category:Suisse]] == Préambule == Waze est une application mobile de navigation pour véhicules. Waze est basé sur un système communautaire. Toutes les cartes sont créées et mises à jour par des utilisateurs de la communauté. Chacun peut apporter sa pierre à l'édifice ! Dans plusieurs pays, Waze a mis en place une carte de base créé de façon automatique. Cette base est toutefois loin d'être parfaite au niveau de la géométrie. De plus, les cartes de base ne contiennent aucune indication sur les noms des rues, noms de villes, types de routes ainsi que sur les autorisations de tourner. En Suisse, nous n'avons pas eu droit à une carte de base. Cela veut dire que toutes les routes doivent être créées par les utilisateurs (traçage, nommage, etc.). Il y a donc un travail conséquent pour obtenir une carte fiable et complète. C'est pourquoi, nous avons besoin de votre aide pour aider l'ensemble de la communauté. == Devenir éditeur de carte == Avant de faire toutes modifications sur la carte, il est nécessaire de lire la documentation en anglais ainsi que la documentation spécifique à la Suisse. Chaque pays dispose de particularité, c'est pourquoi il est nécessaire de se renseigner sur les règles propres à chaque pays. Il existe deux variantes pour éditer la carte : * Editer des routes que vous avez parcouru * Editer une région que vous connaissez === Editer des routes que vous avez parcouru === Lors de l'utilisation de l'application mobile, chacun de vos trajets est enregistré et visible dans votre tableau de bord (My Dashboard). Waze sait par conséquent chaque route que vous avez empruntée. Dès l'instant où vous avez emprunté une route, Waze vous accorde le droit d'éditer cette route sur l'éditeur de carte (WME, Waze Map Editor). Avec ce système vous êtes autorisé à modifier la géométrie, modifier les autorisations de tourner, nommer des routes, etc. Ce droit n'est toutefois pas acquis à vie, après une certaine période, Waze vous retire les droits d'éditions si vous n'avez pas réemprunté cette route dernièrement. === Editer une région que vous connaissez === Si l'édition de la carte vous plaît, vous avez la possibilité de prendre plus de responsabilité en devenant "Area Manager". En devenant Area Manager, vous n'avez plus besoin d'emprunter une route pour obtenir des droits d'éditions sur celle-ci. Vous pouvez devenir Area Manager de votre quartier, votre ville, votre canton voir plus. Pour devenir Area Manager, il faut en faire la demande en remplissant le questionnaire [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Devenir Area Manager] == Permalink == Le permalink est un lien qui se trouve en bas de l'éditeur de carte qui permet d'obtenir un lien de la zone qui est affiché sur votre écran. Ce lien peut s'avérer utile pour obtenir de l'aide sur les forums de discussions. Des informations plus complètes sont disponible sur le [http://www.waze.com/wiki/index.php/Permalink#Permalink Wiki de Waze] (en anglais) == Les serveurs == Waze fonctionne sur trois serveurs distincts, à savoir : * Serveur Etats-Unis, appelé plus fréquemment ''serveur NA'' * Serveur Israel, appelé plus fréquemment ''serveur IL'' * Serveur International (tous les pays sauf les USA et Israel), appelé plus fréquemment ''serveur INTL'' == Données des moteurs de recherche == Les images satellites visible dans l'éditeur de carte sont issues d'un partenariat en Waze et Bing Maps. '''Attention, Bing Maps autorise Waze de l'utilisation unique des images satellites. Vous ne devez en aucun cas recopier une partie des données de Bing Maps ! Il en va de même pour Google Maps.''' Le non-respect de cette règle peut contraindre Waze a supprimer toutes les informations d'un pays s'il est prouvé que des utilisateurs ont utilisé des données de Google Maps ou Bing Maps. Ce cas est déjà arrivé au Chili. [[Switzerland|Retour au Wiki Suisse]] 1185a75b71b9c225a861e0d40979d7c44c877b25 11915 11914 2017-05-03T13:49:15Z Vince1612 23 /* Permalink */ wikitext text/x-wiki [[Category:Suisse]] == Préambule == Waze est une application mobile de navigation pour véhicules. Waze est basé sur un système communautaire. Toutes les cartes sont créées et mises à jour par des utilisateurs de la communauté. Chacun peut apporter sa pierre à l'édifice ! Dans plusieurs pays, Waze a mis en place une carte de base créé de façon automatique. Cette base est toutefois loin d'être parfaite au niveau de la géométrie. De plus, les cartes de base ne contiennent aucune indication sur les noms des rues, noms de villes, types de routes ainsi que sur les autorisations de tourner. En Suisse, nous n'avons pas eu droit à une carte de base. Cela veut dire que toutes les routes doivent être créées par les utilisateurs (traçage, nommage, etc.). Il y a donc un travail conséquent pour obtenir une carte fiable et complète. C'est pourquoi, nous avons besoin de votre aide pour aider l'ensemble de la communauté. == Devenir éditeur de carte == Avant de faire toutes modifications sur la carte, il est nécessaire de lire la documentation en anglais ainsi que la documentation spécifique à la Suisse. Chaque pays dispose de particularité, c'est pourquoi il est nécessaire de se renseigner sur les règles propres à chaque pays. Il existe deux variantes pour éditer la carte : * Editer des routes que vous avez parcouru * Editer une région que vous connaissez === Editer des routes que vous avez parcouru === Lors de l'utilisation de l'application mobile, chacun de vos trajets est enregistré et visible dans votre tableau de bord (My Dashboard). Waze sait par conséquent chaque route que vous avez empruntée. Dès l'instant où vous avez emprunté une route, Waze vous accorde le droit d'éditer cette route sur l'éditeur de carte (WME, Waze Map Editor). Avec ce système vous êtes autorisé à modifier la géométrie, modifier les autorisations de tourner, nommer des routes, etc. Ce droit n'est toutefois pas acquis à vie, après une certaine période, Waze vous retire les droits d'éditions si vous n'avez pas réemprunté cette route dernièrement. === Editer une région que vous connaissez === Si l'édition de la carte vous plaît, vous avez la possibilité de prendre plus de responsabilité en devenant "Area Manager". En devenant Area Manager, vous n'avez plus besoin d'emprunter une route pour obtenir des droits d'éditions sur celle-ci. Vous pouvez devenir Area Manager de votre quartier, votre ville, votre canton voir plus. Pour devenir Area Manager, il faut en faire la demande en remplissant le questionnaire [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Devenir Area Manager] == Permalink == Le permalink est un lien qui se trouve en bas de l'éditeur de carte qui permet d'obtenir un lien de la zone qui est affiché sur votre écran. Ce lien peut s'avérer utile pour obtenir de l'aide sur les forums de discussions. Des informations plus complètes sont disponible sur le [[france:Waze_Map_Editor_(WME)/Zone_d'affichage_de_la_carte#Permalien|cette page]]. == Les serveurs == Waze fonctionne sur trois serveurs distincts, à savoir : * Serveur Etats-Unis, appelé plus fréquemment ''serveur NA'' * Serveur Israel, appelé plus fréquemment ''serveur IL'' * Serveur International (tous les pays sauf les USA et Israel), appelé plus fréquemment ''serveur INTL'' [[Switzerland|Retour au Wiki Suisse]] 417543918f90ae28c42772d631ed229f794c1305 0 18 11923 10991 2017-05-08T08:08:19Z Thierrym 31 orthographe wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Highways== * <span style="color:RoyalBlue;">'''Freeway'''</span> => Autoroute * <span style="color:RoyalBlue;">'''Major Highway'''</span> => Semi-autoroute * <span style="color:RoyalBlue;">'''Minor Highway'''</span> => Route nationale et principale * <span style="color:RoyalBlue;">'''Ramps'''</span> => Entrées et sorties d'autoroutes ==Streets== * <span style="color:RoyalBlue;">'''Primary Street'''</span> => Route principale * <span style="color:RoyalBlue;">'''Street'''</span> => Toutes les autres rues, rues secondaires, etc. * <span style="color:RoyalBlue;">'''Service Road'''</span> => Route d'accès à des services ( essence, restaurant, magasin, Mc Do, etc). ==Other - drivable== * <span style="color:RoyalBlue;">'''Dirt Roads/4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Parking Lot Road'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non-drivable== * <span style="color:RoyalBlue;">'''Walking Trails'''</span> => Chemin pédestre * <span style="color:RoyalBlue;">'''Pedestrian Boardwalk'''</span> => Zone piétonne, bords de lac * <span style="color:RoyalBlue;">'''Stairway'''</span> => Escalier * <span style="color:RoyalBlue;">'''Railroad'''</span> => Chemin de fer * <span style="color:RoyalBlue;">'''Runway/Taxiway'''</span> => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseilé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principale <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] bb4489d4ea2c5a76516890d62c76fee68c098bbd 10 75 11924 2017-05-21T14:52:51Z Wottem 21 Created page with "'''TestMe'''" wikitext text/x-wiki '''TestMe''' 4ad80d7bb1f61a438da08a517313d1a8f953ad71 11925 11924 2017-05-21T17:07:09Z Wottem 21 1 Version von [[:global:Template:TestMe]] importiert: Bot Script Sync Templates wikitext text/x-wiki '''TestMe''' 4ad80d7bb1f61a438da08a517313d1a8f953ad71 0 1 11926 11919 2017-07-01T13:31:29Z Vince1612 23 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div>- ==== Pour les francophones ==== '''Veuillez suivre ce lien pour obtenir des [[Informations en français]].''' -<br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 235d1a34b3e4af18c3008a296914ffb96db5f6ea 11927 11926 2017-07-01T13:32:29Z Vince1612 23 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div>- == Pour les francophones == '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]].''' -<br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 7f1605e19a6c52f73b24754613334df0e5ecc3d3 11928 11927 2017-07-01T13:32:51Z Vince1612 23 /* Pour les francophones */ wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div>- == Pour les francophones == '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]].''' <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] e7da928545ac6f22a8a97cb81f7f7fcb23a57a4a 11929 11928 2017-07-01T13:40:25Z Vince1612 23 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands (suisses francophones)</p> Veuillez suivre le lien suivant pour obtenir des '''[[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] d33d7ed33a14f3fde67bf1db851d9b9ee4542120 11942 11929 2017-07-02T09:45:53Z Vince1612 23 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands (suisses francophones)</p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 5e6b511c5830ef57c78f7f371ef7b09ded1954c2 11943 11942 2017-07-02T09:54:11Z Vince1612 23 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone] und lies die [[Anleitung für Benutzer]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 8fd06cdd0be462e3668743ad9e3164332887080d 0 74 11930 11922 2017-07-01T13:51:38Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * ...plus à venir '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [[france:Accueil|Accueil]] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' f42ea6bd061477e190b55e70180e85a6efeefd5c 11931 11930 2017-07-01T13:52:14Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [[france:Accueil|Accueil]] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' c6baaf5cef236ff9559f879359c03914d54e96c9 11932 11931 2017-07-01T14:11:34Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [[Waze Map Editor (WME)]] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' c1173a4479b7755e00867a31f04c848cd00bdfa2 11933 11932 2017-07-01T14:12:40Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possibles ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 42db5ba477f84f0e0d96b1dae833f3525d4fc29c 11934 11933 2017-07-02T08:42:23Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 46085ff2447dd48837988884faa24448f42f2353 11936 11934 2017-07-02T08:54:35Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Virages difficiles]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 6e28279730ac7414701e7694b2c3d4f456e27084 11941 11936 2017-07-02T09:23:52Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Virages difficiles]] * [[Fermeture des URs]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 2ef435425f28114f593638805bfee1872a5ad244 11944 11941 2017-07-02T10:14:07Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Virages difficiles]] * [[Fermeture des URs]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions'''<ref>'''Cas de 2016''' En voyant que nous ne cartographions pas les voies des parkings de la même façon, un éditeur d'un pays voisin a totalement refait des centaines de parkings en Suisse romande. Au lieu de chercher à connaître les règles locales, il a supposé que tous nos parkings étaient faux et qu'il pouvait donc tous les refaires. Ceci a engendré plusieurs heures de corrections laborieuses et désagréables. Merci donc de ne pas faire de suppositions menant à des centaines d'éditions, demandez avant de tout changer. Merci </ref>'''. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' f4c3f55640f36ca2a953c6afb764996fac4e244d 11945 11944 2017-07-02T10:14:58Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Virages difficiles]] * [[Fermeture des URs]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 2ef435425f28114f593638805bfee1872a5ad244 11947 11945 2017-08-04T05:44:23Z Vince1612 23 Ajout lien wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Règles d'édition en Suisse romande]] * [[Fermeture des URs]] * [[Virages difficiles]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' 27dd3d133dc317f88566b7388bf0846969b74f98 11958 11947 2017-08-04T08:30:08Z Vince1612 23 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Règles d'édition en Suisse romande|'''Règles d'édition en Suisse romande''']] * [[Fermeture des URs]] * [[Virages difficiles]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' ad4a02536179f2313a9f6ded898334ada89c098f 11970 11958 2017-08-16T19:13:10Z Cedricvondk 34 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Règles d'édition en Suisse romande|'''Règles d'édition en Suisse romande''']] * [[Fermeture des URs]] * [[Virages difficiles]] * Guide des intersections * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' f548ea252621485ba27c7fa13ceaf4bf1092d148 11971 11970 2017-08-16T19:14:29Z Cedricvondk 34 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Règles d'édition en Suisse romande|'''Règles d'édition en Suisse romande''']] * [[Fermeture des URs]] * [[Virages difficiles]] * [[Guide des intersections]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' e3e45762f15ff04dd1f1661d27d9b8cced67920d 11972 11971 2017-08-16T19:22:38Z Cedricvondk 34 wikitext text/x-wiki Le wiki Suisse francophone est sensé être une traduction de la version allemande. Malheureusement, des retards de mises à jours et de finalisations d'articles en allemand ne permettent pas d'effectuer des traductions pour le moment. Veuillez donc retenir que le Wiki faisant foi pour l'édition en Suisse est en principe le wiki germanophone, cependant tout le monde ne parlant pas allemand, nous allons tenter de vous fournir le plus d'informations possible ici tout de même. '''Articles existants sur l'édition en de carte <u>en Suisse</u> et copies de publications du forum romand''' * [[A propos de l'édition]] * [[Légende de la Carte Suisse]] * [[Comment nommer les routes et les villes en Suisse]] * [[Règles d'édition en Suisse romande|'''Règles d'édition en Suisse romande''']] * [[Fermeture des URs]] * [[Virages difficiles]] * ...plus à venir <br> '''IMPORTANT''' * Les autres informations et règles importantes relatives à l'édition en Suisse en français se trouvent le plus souvent sur le forum local de Suisse romande, merci d'y lire les sujets épinglés en haut du forum. Lien vers le forum: [https://www.waze.com/forum/viewforum.php?f=836 Romandie] * Pour tout ce qui est relatif à l'utilisation de WME <u>sur l'aspect technique uniquement</u> (aucunement en ce qui concerne les règles d'édition), merci de vous référer à la page du Wiki de France disponible ici: [https://wazeopedia.waze.com/wiki/France/Waze_Map_Editor_%28WME%29 Waze Map Editor (WME)] * <u>'''VEUILLEZ NOTER:'''</u> '''En cas de doute, de manque d'information ou toute autre situation similaire, veuillez ne <u>jamais</u> faire de modification sur WME en Suisse romande en vous basant sur des règles d'édition de pays voisins ou en faisant des suppositions. Veuillez toujours rédiger votre question sur notre forum local mentionné ci-dessus et nous y répondrons le plus rapidement possible.''' ad4a02536179f2313a9f6ded898334ada89c098f 0 76 11935 2017-07-02T08:53:40Z Vince1612 23 New page for th Swiss wiki in French wikitext text/x-wiki [[Datei:Virages difficiles.jpeg|mini|Virages difficiles]] '''Sur l'application''' Allez dans Réglages - Navigation et vous remarquerez le nouveau réglage vous permettant d'indiquer à Waze si vous préférez éviter les virages difficiles ou non. '''Sur WME''' Waze ne décide pas automatiquement quels virages sont difficiles, il appartient à la communauté locale de les indiquer comme tels dans WME. Cette fonction est disponible via le même menu que les restrictions de circulation pour les flèches d'autorisation de tourner et est activable via une case à cocher, tout simplement. Il n'y a aucune restriction d'utilisation par niveau pour cette fonction. Pouvoir la modifier dépend donc du niveau de verrouillage du segment ainsi que du niveau d'édition de l'éditeur. '''Effets et recommandations''' Marquer un virage comme difficile le pénalisera 24/24h et 7/7j - Il n'est pas possible ou prévu pour l'instant de pouvoir régler des jours ou horaires particuliers. Merci donc de bien vouloir observer ces quelques indications: * Cette fonction a été créée à la base pour des carrefours sans feux et lorsque tourner à droite est simple, mais que de traverser ou de tourner à gauche peut être très difficile à réaliser en raison du trafic prioritaire (voir illustration ci-dessus). Chaque Wazer peut ensuite décider ou nom via le réglage de l'application s'il souhaite que Waze les évites ou non. * Le réglage a été activé par défaut pour tout le monde - À noter donc que tout ajout de virage difficile impactera 95% des utilisateurs en supposant que seuls 5% auront remarqué l'apparition ce nouveau réglage et éventuellement choisi de le désactiver. * Merci de n'appliquer cette pénalité que lorsque cela vous semble vraiment nécessaire, car en raison de l'effet permanent et de l'activation par défaut, ce même virage sera également pénalisé en cas de faible trafic routier ou durant la nuit, ce qui pourrait causer une certaine incompréhension chez certains Wazers. * Merci de ne pas utiliser cette fonction sur des carrefours équipés de feux de signalisation (même si le rouge est "très long").<br>L'algorithme chargé de calculer la vitesse moyenne de temps de passage sur le segment de A à B devrait en principe déjà prendre en compte un temps de passage plus long et s'adapter aux conditions du trafic en se basant sur es données historiques et en temps réel. Ce qui est préférable à un effet négatif permanent. d6b92d2640448aaf08027435bbf8992f9152fdc6 0 77 11937 2017-07-02T09:08:50Z Vince1612 23 New page French speaking Switzerland wiki wikitext text/x-wiki Les règles de fermetures des signalements d'erreurs de carte (''UR - "User Report"'') en Suisse sont les suivantes: '''Solved (corrigé)''' * Si vous pouvez identifier la raison du signalement <u>et</u> que vous êtes capable de corriger le problème dans l'éditeur, que vous parvenez à faire la modification <u>et</u> sauvegarder correctement. Alors '''à ce moment vous pouvez marquer l'UR comme corrigé'''. '''Not identified (non identifié)''' * Si pour plusieurs raisons, comme le manque de détails ou des conflits entre le tracé GPS et la route suggérée, vous ne parvenez pas à trouver la raison du signalement. Dans ces cas là, vous devriez tenter d'entrer en communication avec l'auteur du signalement. * Si une conversation a déjà été initiée par un autre éditeur et qu'un temps raisonnable a passé depuis les dernières informations fournies par l'auteur du signalement, vous pouvez laisser un message pour suggérer que l'UR soit fermé. Il est préférable d'attendre une réaction de l'autre éditeur avant de prendre action vous-même sur l'UR. * Si vous ne recevez pas de réponse dans un délai raisonnable après avoir posé des questions vous pouvez considérer l'option de fermer l'UR en non identifié.<br>Mais aussi, parfois des utilisateurs signalent des problèmes valides, mais qui ne peuvent pas être corrigés dans l'éditeur de carte. Ces signalement devraient eux-aussi être fermés comme non identifiés, avec une explication à l'auteur du signalement que le problème signalé ne peut pas ou ne sera pas corrigé dans l'éditeur. <br> '''Merci donc à tous de ne fermer les UR comme corrigé que si toutes les conditions citées ci-dessus sont remplies, et <u>ceci peu importe si la discussion dans le chat de l'UR a apporté une réponse ou une solution mais qu'aucune modification de carte n'a été effectuée.</u>'''<br> '''Pourquoi insister là-dessus?''' Outre le fait que de noter un UR comme corrigé sans avoir fait de modifications ou de corrections n'est pas approprié, vous devez prendre en compte que l'auteur de l'UR reçoit lui aussi des notifications du système immédiatement après une fermeture de son signalement. Un exemple de mail reçu lorsque l'UR est fermé comme corrigé: ''Hi vince1612, <br> <br> '''The map issue you reported''' from 11.09.2016 on Álafossvegur, Mosfellsbær ("Dead end. Concrete blocks blocking the road") '''was fixed''' by tbk0. '''The map has been updated accordingly'''. You've helped many wazers. Thanks!<br> <br> '''You can see the fixed area in the Waze map editor here''' <nowiki>https://www.waze.com/editor/?zoom=5&lat</nowiki> ... 28&env=row<br> <br> Want to join the map editing community? Here’s how to start:<br> How to edit the Waze map video tutorial - <nowiki>http://www.youtube.com/watch?v=HVksbb1Z4SQ</nowiki><br> Map Editing wiki - <nowiki>https://www.waze.com/wiki/index.php/Waze_Map_Editor</nowiki><br> Waze editing forum - viewforum.php?f=8'' Essentiellement si on informe un utilisateur via le chat que son problème ne sera pas corrigé ou ne pourra pas l'être, ou même que l'on réponde à sa question mais toujours sans modifier la carte. Il est très contradictoire qu'il reçoive directement par la suite un message l'informant: * Que le problème qu'il a signalé a été résolu - faux * Que la carte a été mise à jour - faux * Qu'il a aidé beaucoup de Wazer et qu'il est remercié - c'est l'intention qui compte, mais faux * Qu'il peut voir les corrections faites dans l'éditeur avec le permalink fourni - archi-faux <br> D'autant plus que ceci est aussi ce qu'il reçoit sur son application en plus de l'e-mail. b9be2519756d155f4c9db46c9340012993f03ad8 11938 11937 2017-07-02T09:17:49Z Vince1612 23 wikitext text/x-wiki <big>'''Les règles de fermetures des signalements d'erreurs de carte (''UR - "User Report"'') en Suisse sont les suivantes:'''</big> '''Solved (corrigé)''' * Si vous pouvez identifier la raison du signalement <u>et</u> que vous êtes capable de corriger le problème dans l'éditeur, que vous parvenez à faire la modification <u>et</u> sauvegarder correctement. Alors '''à ce moment vous pouvez marquer l'UR comme corrigé'''. '''Not identified (non identifié)''' * Si pour plusieurs raisons, comme le manque de détails ou des conflits entre le tracé GPS et la route suggérée, vous ne parvenez pas à trouver la raison du signalement. Dans ces cas là, vous devriez tenter d'entrer en communication avec l'auteur du signalement. * Si une conversation a déjà été initiée par un autre éditeur et qu'un temps raisonnable a passé depuis les dernières informations fournies par l'auteur du signalement, vous pouvez laisser un message pour suggérer que l'UR soit fermé. Il est préférable d'attendre une réaction de l'autre éditeur avant de prendre action vous-même sur l'UR. * Si vous ne recevez pas de réponse dans un délai raisonnable après avoir posé des questions vous pouvez considérer l'option de fermer l'UR en non identifié.<br>Mais aussi, parfois des utilisateurs signalent des problèmes valides, mais qui ne peuvent pas être corrigés dans l'éditeur de carte. Ces signalement devraient eux-aussi être fermés comme non identifiés, avec une explication à l'auteur du signalement que le problème signalé ne peut pas ou ne sera pas corrigé dans l'éditeur. <br> '''Merci donc à tous de ne fermer les UR comme corrigé que si toutes les conditions citées ci-dessus sont remplies, et <u>ceci peu importe si la discussion dans le chat de l'UR a apporté une réponse ou une solution mais qu'aucune modification de carte n'a été effectuée.</u>'''<br> <big>'''Pourquoi insister là-dessus?'''</big> Outre le fait que de noter un UR comme corrigé sans avoir fait de modifications ou de corrections n'est pas approprié, vous devez prendre en compte que l'auteur de l'UR reçoit lui aussi des notifications du système immédiatement après une fermeture de son signalement. Un exemple de mail reçu lorsque l'UR est fermé comme corrigé: <br> <small>''Hi vince1612, <br><br> <span style="color:#0000FF">The map issue you reported</span> from 11.09.2016 on Álafossvegur, Mosfellsbær ("Dead end. Concrete blocks blocking the road") <span style="color:#0000FF">was fixed by tbk0</span>. <span style="color:#0000FF">The map has been updated accordingly</span>. You've helped many wazers. Thanks!<br><br> <span style="color:#0000FF">You can see the fixed area in the Waze map editor here</span> <nowiki>https://www.waze.com/editor/?zoom=5&lat</nowiki> ... 28&env=row''</small> <br><br><br> Essentiellement si on informe un utilisateur via le chat que son problème ne sera pas corrigé ou ne pourra pas l'être, ou même que l'on réponde à sa question mais toujours sans modifier la carte. Il est très <u>contradictoire</u> qu'il reçoive directement par la suite un message l'informant: * Que le problème qu'il a signalé a été résolu - <span style="color:red">faux</span> * Que la carte a été mise à jour - <span style="color:red">faux</span> * Qu'il a aidé beaucoup de Wazer et qu'il est remercié - c'est l'intention qui compte, mais <span style="color:red">faux</span> * Qu'il peut voir les corrections faites dans l'éditeur avec le permalink fourni - <span style="color:red">archi-faux</span> <br> D'autant plus que ceci est aussi ce qu'il reçoit sur son application en plus de l'e-mail. a3cb9894a88b68bfa93ae7d1fa2b1e68c5cbb3c7 11939 11938 2017-07-02T09:19:28Z Vince1612 23 wikitext text/x-wiki <big>'''Les règles de fermetures des signalements d'erreurs de carte (''UR - "User Report"'') en Suisse sont les suivantes:'''</big> '''Solved (corrigé)''' * Si vous pouvez identifier la raison du signalement <u>et</u> que vous êtes capable de corriger le problème dans l'éditeur, que vous parvenez à faire la modification <u>et</u> sauvegarder correctement. Alors '''à ce moment vous pouvez marquer l'UR comme corrigé'''. '''Not identified (non identifié)''' * Si pour plusieurs raisons, comme le manque de détails ou des conflits entre le tracé GPS et la route suggérée, vous ne parvenez pas à trouver la raison du signalement. Dans ces cas là, vous devriez tenter d'entrer en communication avec l'auteur du signalement. * Si une conversation a déjà été initiée par un autre éditeur et qu'un temps raisonnable a passé depuis les dernières informations fournies par l'auteur du signalement, vous pouvez laisser un message pour suggérer que l'UR soit fermé. Il est préférable d'attendre une réaction de l'autre éditeur avant de prendre action vous-même sur l'UR. * Si vous ne recevez pas de réponse dans un délai raisonnable après avoir posé des questions vous pouvez considérer l'option de fermer l'UR en non identifié.<br>Mais aussi, parfois des utilisateurs signalent des problèmes valides, mais qui ne peuvent pas être corrigés dans l'éditeur de carte. Ces signalement devraient eux-aussi être fermés comme non identifiés, avec une explication à l'auteur du signalement que le problème signalé ne peut pas ou ne sera pas corrigé dans l'éditeur. <br> '''Merci donc à tous de ne fermer les UR comme corrigé que si toutes les conditions citées ci-dessus sont remplies, et <u>ceci peu importe si la discussion dans le chat de l'UR a apporté une réponse ou une solution mais qu'aucune modification de carte n'a été effectuée.</u>'''<br> <big>'''Pourquoi insister là-dessus?'''</big> Outre le fait que de noter un UR comme corrigé sans avoir fait de modifications ou de corrections n'est pas approprié, vous devez prendre en compte que l'auteur de l'UR reçoit lui aussi des notifications du système immédiatement après une fermeture de son signalement. Un exemple de mail reçu lorsque l'UR est fermé comme corrigé: <br><small>''Hi vince1612, <br><br><span style="color:#0000FF">The map issue you reported</span> from 11.09.2016 on Álafossvegur, Mosfellsbær ("Dead end. Concrete blocks blocking the road") <span style="color:#0000FF">was fixed by tbk0</span>. <span style="color:#0000FF">The map has been updated accordingly</span>. You've helped many wazers. Thanks!<br><br><span style="color:#0000FF">You can see the fixed area in the Waze map editor here</span> <nowiki>https://www.waze.com/editor/?zoom=5&lat</nowiki> ... 28&env=row''</small><br><br><br>Essentiellement si on informe un utilisateur via le chat que son problème ne sera pas corrigé ou ne pourra pas l'être, ou même que l'on réponde à sa question mais toujours sans modifier la carte. Il est très <u>contradictoire</u> qu'il reçoive directement par la suite un message l'informant: * Que le problème qu'il a signalé a été résolu - <span style="color:red">faux</span> * Que la carte a été mise à jour - <span style="color:red">faux</span> * Qu'il a aidé beaucoup de Wazer et qu'il est remercié - c'est l'intention qui compte, mais <span style="color:red">faux</span> * Qu'il peut voir les corrections faites dans l'éditeur avec le permalink fourni - <span style="color:red">archi-faux</span> <br>D'autant plus que ceci est aussi ce qu'il reçoit sur son application en plus de l'e-mail. 4916c44f4b58f466bbc06cd6e42b58371e760a3b 11940 11939 2017-07-02T09:22:25Z Vince1612 23 wikitext text/x-wiki <big>'''Les règles de fermetures des signalements d'erreurs de carte (''UR - "User Report"'') en Suisse sont les suivantes:'''</big> '''Solved (corrigé)''' * Si vous pouvez identifier la raison du signalement <u>et</u> que vous êtes capable de corriger le problème dans l'éditeur, que vous parvenez à faire la modification <u>et</u> sauvegarder correctement. Alors '''à ce moment vous pouvez marquer l'UR comme corrigé'''. <br> '''Not identified (non identifié)''' * Si pour plusieurs raisons, comme le manque de détails ou des conflits entre le tracé GPS et la route suggérée, vous ne parvenez pas à trouver la raison du signalement. Dans ces cas là, vous devriez tenter d'entrer en communication avec l'auteur du signalement. * Si une conversation a déjà été initiée par un autre éditeur et qu'un temps raisonnable a passé depuis les dernières informations fournies par l'auteur du signalement, vous pouvez laisser un message pour suggérer que l'UR soit fermé. Il est préférable d'attendre une réaction de l'autre éditeur avant de prendre action vous-même sur l'UR. * Si vous ne recevez pas de réponse dans un délai raisonnable après avoir posé des questions vous pouvez considérer l'option de fermer l'UR en non identifié.<br>Mais aussi, parfois des utilisateurs signalent des problèmes valides, mais qui ne peuvent pas être corrigés dans l'éditeur de carte. Ces signalement devraient eux-aussi être fermés comme non identifiés, avec une explication à l'auteur du signalement que le problème signalé ne peut pas ou ne sera pas corrigé dans l'éditeur. <br> '''Merci donc à tous de ne fermer les UR comme corrigé que si toutes les conditions citées ci-dessus sont remplies, et <u>ceci peu importe si la discussion dans le chat de l'UR a apporté une réponse ou une solution mais qu'aucune modification de carte n'a été effectuée.</u>'''<br> <big>'''Pourquoi insister là-dessus?'''</big> Outre le fait que de noter un UR comme corrigé sans avoir fait de modifications ou de corrections n'est pas approprié, vous devez prendre en compte que l'auteur de l'UR reçoit lui aussi des notifications du système immédiatement après une fermeture de son signalement. Un exemple de mail reçu lorsque l'UR est fermé comme corrigé: <br><blockquote><small>''Hi vince1612, <br><br><span style="color:#0000FF">The map issue you reported</span> from 11.09.2016 on Álafossvegur, Mosfellsbær ("Dead end. Concrete blocks blocking the road") <span style="color:#0000FF">was fixed by tbk0</span>. <br><span style="color:#0000FF">The map has been updated accordingly</span>. You've helped many wazers. Thanks!<br><br><span style="color:#0000FF">You can see the fixed area in the Waze map editor here</span> <nowiki>https://www.waze.com/editor/?zoom=5&lat</nowiki> ... 28&env=row''</small></blockquote><br><br>Essentiellement si on informe un utilisateur via le chat que son problème ne sera pas corrigé ou ne pourra pas l'être, ou même que l'on réponde à sa question mais toujours sans modifier la carte. Il est très <u>contradictoire</u> qu'il reçoive directement par la suite un message l'informant: * Que le problème qu'il a signalé a été résolu - <span style="color:red">faux</span> * Que la carte a été mise à jour - <span style="color:red">faux</span> * Qu'il a aidé beaucoup de Wazer et qu'il est remercié - c'est l'intention qui compte, mais <span style="color:red">faux</span> * Qu'il peut voir les corrections faites dans l'éditeur avec le permalink fourni - <span style="color:red">archi-faux</span> <br>D'autant plus que ceci est aussi ce qu'il reçoit sur son application en plus de l'e-mail. 4c64e86d7bb5c0516042b7e5eba70d4738f39b86 11946 11940 2017-07-04T09:46:45Z Vince1612 23 ajout précision wikitext text/x-wiki ===== <big>'''Les règles de fermetures des signalements d'erreurs de carte (''UR - "User Report"'') en Suisse sont les suivantes:'''</big> ===== '''Solved (corrigé)''' * Si vous pouvez identifier la raison du signalement <u>et</u> que vous êtes capable de corriger le problème dans l'éditeur, que vous parvenez à faire la modification <u>et</u> sauvegarder correctement. Alors '''à ce moment vous pouvez marquer l'UR comme corrigé'''. <br> '''Not identified (non identifié)''' * Si pour plusieurs raisons, comme le manque de détails ou des conflits entre le tracé GPS et la route suggérée, vous ne parvenez pas à trouver la raison du signalement. Dans ces cas là, vous devriez tenter d'entrer en communication avec l'auteur du signalement. * Si une conversation a déjà été initiée par un autre éditeur et qu'un temps raisonnable a passé depuis les dernières informations fournies par l'auteur du signalement, vous pouvez laisser un message pour suggérer que l'UR soit fermé. Il est préférable d'attendre une réaction de l'autre éditeur avant de prendre action vous-même sur l'UR. * Si vous ne recevez pas de réponse dans un délai raisonnable après avoir posé des questions vous pouvez considérer l'option de fermer l'UR en non identifié.<br>Mais aussi, parfois des utilisateurs signalent des problèmes valides, mais qui ne peuvent pas être corrigés dans l'éditeur de carte. Ces signalement devraient eux-aussi être fermés comme non identifiés, avec une explication à l'auteur du signalement que le problème signalé ne peut pas ou ne sera pas corrigé dans l'éditeur. <br> '''Merci donc à tous de ne fermer les UR comme corrigé que si toutes les conditions citées ci-dessus sont remplies, et <u>ceci peu importe si la discussion dans le chat de l'UR a apporté une réponse ou une solution mais qu'aucune modification de carte n'a été effectuée.</u>''' ====== <br> <big>'''Pourquoi insister là-dessus?'''</big> ====== Outre le fait que de noter un UR comme corrigé sans avoir fait de modifications ou de corrections n'est pas approprié, vous devez prendre en compte que l'auteur de l'UR reçoit lui aussi des notifications du système immédiatement après une fermeture de son signalement. Un exemple de mail reçu lorsque l'UR est fermé comme corrigé: <br><blockquote><small>''Hi vince1612, <br><br><span style="color:#0000FF">The map issue you reported</span> from 11.09.2016 on Álafossvegur, Mosfellsbær ("Dead end. Concrete blocks blocking the road") <span style="color:#0000FF">was fixed by tbk0</span>. <br><span style="color:#0000FF">The map has been updated accordingly</span>. You've helped many wazers. Thanks!<br><br><span style="color:#0000FF">You can see the fixed area in the Waze map editor here</span> <nowiki>https://www.waze.com/editor/?zoom=5&lat</nowiki> ... 28&env=row''</small></blockquote><br><br>Essentiellement si on informe un utilisateur via le chat que son problème ne sera pas corrigé ou ne pourra pas l'être, ou même que l'on réponde à sa question mais toujours sans modifier la carte. Il est très <u>contradictoire</u> qu'il reçoive directement par la suite un message l'informant: * Que le problème qu'il a signalé a été résolu - <span style="color:red">faux</span> * Que la carte a été mise à jour - <span style="color:red">faux</span> * Qu'il a aidé beaucoup de Wazer et qu'il est remercié - c'est l'intention qui compte, mais <span style="color:red">faux</span> * Qu'il peut voir les corrections faites dans l'éditeur avec le permalink fourni - <span style="color:red">archi-faux</span> <br>D'autant plus que ceci est aussi ce qu'il reçoit sur son application en plus de l'e-mail. ===== Note sur le signalement "Mauvais sens de circulation" ===== En cas d'UR comprenant le titre ci-dessus, veuillez considérer la chose suivante: Le texte d'origine de ce signalement est "Wrong driving direction", ceci a causé pas mal de confusion lors de la traduction car en anglais le mot "direction" peut autant signifier '<nowiki/>''sens'' de circulation' qu'il peut signifier '''instruction'' de navigation ou de conduite'. Suivant la langue dans laquelle le Wazer utilise l'application Waze, il peut donc soit vouloir signaler une erreur dans le sens de circulation, soit vouloir signaler qu'il a reçu de mauvaises instructions de navigation/guidage pour une étape de son parcours ou pour sa destination finale. Il convient donc dans ces cas là d'entamer une discussion dans l'UR et de demander des précisions. Seul moyen de pouvoir être sûr. f6de8fbfdf6345da405c1030b414cf2facab36dd 0 78 11948 2017-08-04T07:19:08Z Vince1612 23 Nouvelle page règles suisse romande wikitext text/x-wiki (WORK IN PROGRESS!) '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' Parkings, campings, aire de stationnement : Représenter <nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affiche sur les smartphones et ne sert pas à <nowiki> </nowiki>grand chose en fin de compte. Pour les parkings, seuls les segments des entrées et sorties devraient être cartographié et de créer un landmark (Point d'intérêt) de type "Parking". Cette recommandation s'applique aussi pour les campings et autres aire de stationnement. Exemple à suivre : Exemple peu recommandable : Les voies privées (habitation) : Cartographier <nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route ne représente aucun intérêt pour la navigation et alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'au porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la <nowiki> </nowiki>bonne maison. Exemple à suivre : Exemple <nowiki> </nowiki>à ne pas suivre. Il y a énormément d'intersections ce qui augmente le risque de mauvaise manipulation d'un éditeur peu expérimenté. L'affichage sur un smartphone devient lourd et n'apporte finalement aucun intérêt pour la quasi totalité des Wazers. Demi-tours : Pour rappel, la petite flèche verte qui apparaît en fin d'une impasse ne devrait en principe jamais être mise en vert <nowiki> </nowiki>car cela veut dire que des Wazers pourront être guidés sur cette impasse pour faire demi-tour. Pour faire demi-tour si un Wazer s'est trompé, il devrait le faire au prochain giratoire, parking, ou autres mais pas dans une petite rue/impasse. Exemple d'un endroit où le demi-tour est autorisé : Source Wiki (anglais) : <nowiki>https://www.waze.com/wiki/Map_Editing_Q</nowiki> ... nd-streets Nommage : Après <nowiki> </nowiki>avoir fait un survol de la Suisse, mais plus particulièrement de la Suisse romande, je me suis rendu compte que le canton du Valais était plutôt bien cartographier mais malheureusement le nommage n'est pas très <nowiki> </nowiki>abouti. Je peux faire une grande liste de villages qui ne sont pas du tout nommés (Ville et rue) ! D'un <nowiki> </nowiki>point de vue personnel, je préfère privilégier la qualité à la quantité. A quoi bon cartographier des villages/région en entier si la majorité des segments ne sont pas localisables par leurs noms de rues et <nowiki> </nowiki>leurs noms de ville/villages ? Voici <nowiki> </nowiki>encore un exemple de pratiques d'éditions que je ne peux pas comprendre <nowiki> </nowiki>alors que nous disposons d'images aériennes de bonnes qualités depuis plusieurs mois maintenant dans une grande partie de la Suisse. Dans l'exemple ci-dessous, les éditions sont faites à la va-vite, segments tracés à l'équerre, manque le nom de la rue et de la ville. Bref, un <nowiki> </nowiki>travail de basse qualité qui n'apporte à l'heure actuelle aucun avantage pour le Wazer qui doit circuler dessus et en plus un éditeur devra grosso modo tout refaire : Cliquer pour agrandir l'image Autre <nowiki> </nowiki>petit détail, mais lors du nommage des noms de rues, il ne faut pas faire d'abréviation. De plus il y a lieu de respecter la casse des noms de propres (Majuscule au nom des rues). Par exemple : Chemin et non Ch. Route et non Rte Rue de la Paix et non "rue de la paix" Etc. Exemple à ne pas reproduire Segments trop courts Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Segment_length#Too_short</nowiki> La <nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze <nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de <nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de <nowiki> </nowiki>données complètes pour ses calculs. Exemple d'un segment trop court (4m) Solution possible Vous pouvez aussi éloigner les deux nodes pour que le segment mesure au minimum 5m. La longueur d'un segment se voit en cliquant dessus puis dans le menu à gauche : <br> <br> <br> Parking Lot (Places)<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Places/Parking_lot</nowiki><br> <br> J'ai <nowiki> </nowiki>repéré pas mal d'ajouts de zones de parkings sur des places en bord de route. Celles-ci ne sont pas des aires de parking et ne devrait donc pas <nowiki> </nowiki>être cartographiées.<br> L'utilisation de ce repère est réservé aux parkings publics possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation.<br> <br> Exemple à éviter<br> <br> <br> Veillez aussi également à ne pas créer plusieurs parkings là où il y en a en fait un seul:<br> <br> <br> <br> Autres détails<br> <br> À éviter : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br> Correct : Utiliser la catégorie "Parking Lot"<br> <br> À éviter : Nommer le parking comme "Parc"; "Parking"; "P."<br> Correct : Nommer avec le nom exacte (ex. "Parking du Mont-Blanc") ou laisser le champ vide.<br> <br> <br> Parking Lot Roads<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Best_map_edi</nowiki> ... rking_Lots<br> <br> Lorsqu'on <nowiki> </nowiki>cartographie le but est l'utilisabilité et la simplicité de la carte. Pour les parkings donc on essaie de ne cartographier que le nécessaire:<br> <br> - Les entrées/sorties connectées aux routes du réseau routier<br> - Les voies qui longent le(s) commerce(s) ou bâtiment(s)<br> - <nowiki> </nowiki>Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien)<br> - Les voies principales qui servent à passer d'une zone du parking à une autre.<br> <br> À éviter<br> <br> <br> Exemple à suivre<br> <br> <br> En <nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir de cartographier chaque place de parc individuelle (oui, certain l'ont fait... )<br> <br> Représenter <nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. Ceci <nowiki> </nowiki>n'est qu'une liste subjective après un survol fait dans la journée. La lecture du Wiki reste primordial et pas seulement une fois. Le Wiki Suisse <nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent, ces nouveaux articles se trouvent sur le Wiki en anglais faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum 5243d71570b49531ea4390ab6495578484cae7af 11949 11948 2017-08-04T07:24:01Z Vince1612 23 wikitext text/x-wiki (WORK IN PROGRESS!) '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' === '''Parkings et aires de stationnement''' === Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affiche sur les smartphones et ne sert pas à<nowiki> </nowiki>grand chose en fin de compte. Pour les parkings, seuls les segments des entrées et sorties devraient être cartographié et de créer un landmark (Point d'intérêt) de type "Parking". Cette recommandation s'applique aussi pour les campings et autres aire de stationnement. Exemple à suivre : Exemple peu recommandable : Les voies privées (habitation) : Cartographier <nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route ne représente aucun intérêt pour la navigation et alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'au porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la <nowiki> </nowiki>bonne maison. Exemple à suivre : Exemple <nowiki> </nowiki>à ne pas suivre. Il y a énormément d'intersections ce qui augmente le risque de mauvaise manipulation d'un éditeur peu expérimenté. L'affichage sur un smartphone devient lourd et n'apporte finalement aucun intérêt pour la quasi totalité des Wazers. Demi-tours : Pour rappel, la petite flèche verte qui apparaît en fin d'une impasse ne devrait en principe jamais être mise en vert <nowiki> </nowiki>car cela veut dire que des Wazers pourront être guidés sur cette impasse pour faire demi-tour. Pour faire demi-tour si un Wazer s'est trompé, il devrait le faire au prochain giratoire, parking, ou autres mais pas dans une petite rue/impasse. Exemple d'un endroit où le demi-tour est autorisé : Source Wiki (anglais) : <nowiki>https://www.waze.com/wiki/Map_Editing_Q</nowiki> ... nd-streets Nommage : Après <nowiki> </nowiki>avoir fait un survol de la Suisse, mais plus particulièrement de la Suisse romande, je me suis rendu compte que le canton du Valais était plutôt bien cartographier mais malheureusement le nommage n'est pas très <nowiki> </nowiki>abouti. Je peux faire une grande liste de villages qui ne sont pas du tout nommés (Ville et rue) ! D'un <nowiki> </nowiki>point de vue personnel, je préfère privilégier la qualité à la quantité. A quoi bon cartographier des villages/région en entier si la majorité des segments ne sont pas localisables par leurs noms de rues et <nowiki> </nowiki>leurs noms de ville/villages ? Voici <nowiki> </nowiki>encore un exemple de pratiques d'éditions que je ne peux pas comprendre <nowiki> </nowiki>alors que nous disposons d'images aériennes de bonnes qualités depuis plusieurs mois maintenant dans une grande partie de la Suisse. Dans l'exemple ci-dessous, les éditions sont faites à la va-vite, segments tracés à l'équerre, manque le nom de la rue et de la ville. Bref, un <nowiki> </nowiki>travail de basse qualité qui n'apporte à l'heure actuelle aucun avantage pour le Wazer qui doit circuler dessus et en plus un éditeur devra grosso modo tout refaire : Cliquer pour agrandir l'image Autre <nowiki> </nowiki>petit détail, mais lors du nommage des noms de rues, il ne faut pas faire d'abréviation. De plus il y a lieu de respecter la casse des noms de propres (Majuscule au nom des rues). Par exemple : Chemin et non Ch. Route et non Rte Rue de la Paix et non "rue de la paix" Etc. Exemple à ne pas reproduire Segments trop courts Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Segment_length#Too_short</nowiki> La <nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze <nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de <nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de <nowiki> </nowiki>données complètes pour ses calculs. Exemple d'un segment trop court (4m) Solution possible Vous pouvez aussi éloigner les deux nodes pour que le segment mesure au minimum 5m. La longueur d'un segment se voit en cliquant dessus puis dans le menu à gauche : <br> <br> <br> Parking Lot (Places)<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Places/Parking_lot</nowiki><br> <br> J'ai <nowiki> </nowiki>repéré pas mal d'ajouts de zones de parkings sur des places en bord de route. Celles-ci ne sont pas des aires de parking et ne devrait donc pas <nowiki> </nowiki>être cartographiées.<br> L'utilisation de ce repère est réservé aux parkings publics possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation.<br> <br> Exemple à éviter<br> <br> <br> Veillez aussi également à ne pas créer plusieurs parkings là où il y en a en fait un seul:<br> <br> <br> <br> Autres détails<br> <br> À éviter : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br> Correct : Utiliser la catégorie "Parking Lot"<br> <br> À éviter : Nommer le parking comme "Parc"; "Parking"; "P."<br> Correct : Nommer avec le nom exacte (ex. "Parking du Mont-Blanc") ou laisser le champ vide.<br> <br> <br> Parking Lot Roads<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Best_map_edi</nowiki> ... rking_Lots<br> <br> Lorsqu'on <nowiki> </nowiki>cartographie le but est l'utilisabilité et la simplicité de la carte. Pour les parkings donc on essaie de ne cartographier que le nécessaire:<br> <br> - Les entrées/sorties connectées aux routes du réseau routier<br> - Les voies qui longent le(s) commerce(s) ou bâtiment(s)<br> - <nowiki> </nowiki>Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien)<br> - Les voies principales qui servent à passer d'une zone du parking à une autre.<br> <br> À éviter<br> <br> <br> Exemple à suivre<br> <br> <br> En <nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir de cartographier chaque place de parc individuelle (oui, certain l'ont fait... )<br> <br> Représenter <nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. Ceci <nowiki> </nowiki>n'est qu'une liste subjective après un survol fait dans la journée. La lecture du Wiki reste primordial et pas seulement une fois. Le Wiki Suisse <nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent, ces nouveaux articles se trouvent sur le Wiki en anglais faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum 860c1f0b35e096ca645c816879e92d69efb7e6c3 11950 11949 2017-08-04T07:38:05Z Vince1612 23 wikitext text/x-wiki (WORK IN PROGRESS!) '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' === '''Parkings et aires de stationnement''' === ==== Voies de parkings ==== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire:<br>- Les entrées/sorties connectées aux routes du réseau routier<br>- Les voies qui longent le(s) commerce(s) ou bâtiment(s)<br>-<nowiki> </nowiki>Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien)<br>- Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...)<br><br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. Les voies privées (habitation) : Cartographier <nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route ne représente aucun intérêt pour la navigation et alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'au porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la <nowiki> </nowiki>bonne maison. Exemple à suivre : Exemple <nowiki> </nowiki>à ne pas suivre. Il y a énormément d'intersections ce qui augmente le risque de mauvaise manipulation d'un éditeur peu expérimenté. L'affichage sur un smartphone devient lourd et n'apporte finalement aucun intérêt pour la quasi totalité des Wazers. Demi-tours : Pour rappel, la petite flèche verte qui apparaît en fin d'une impasse ne devrait en principe jamais être mise en vert <nowiki> </nowiki>car cela veut dire que des Wazers pourront être guidés sur cette impasse pour faire demi-tour. Pour faire demi-tour si un Wazer s'est trompé, il devrait le faire au prochain giratoire, parking, ou autres mais pas dans une petite rue/impasse. Exemple d'un endroit où le demi-tour est autorisé : Source Wiki (anglais) : <nowiki>https://www.waze.com/wiki/Map_Editing_Q</nowiki> ... nd-streets Nommage : Après <nowiki> </nowiki>avoir fait un survol de la Suisse, mais plus particulièrement de la Suisse romande, je me suis rendu compte que le canton du Valais était plutôt bien cartographier mais malheureusement le nommage n'est pas très <nowiki> </nowiki>abouti. Je peux faire une grande liste de villages qui ne sont pas du tout nommés (Ville et rue) ! D'un <nowiki> </nowiki>point de vue personnel, je préfère privilégier la qualité à la quantité. A quoi bon cartographier des villages/région en entier si la majorité des segments ne sont pas localisables par leurs noms de rues et <nowiki> </nowiki>leurs noms de ville/villages ? Voici <nowiki> </nowiki>encore un exemple de pratiques d'éditions que je ne peux pas comprendre <nowiki> </nowiki>alors que nous disposons d'images aériennes de bonnes qualités depuis plusieurs mois maintenant dans une grande partie de la Suisse. Dans l'exemple ci-dessous, les éditions sont faites à la va-vite, segments tracés à l'équerre, manque le nom de la rue et de la ville. Bref, un <nowiki> </nowiki>travail de basse qualité qui n'apporte à l'heure actuelle aucun avantage pour le Wazer qui doit circuler dessus et en plus un éditeur devra grosso modo tout refaire : Cliquer pour agrandir l'image Autre <nowiki> </nowiki>petit détail, mais lors du nommage des noms de rues, il ne faut pas faire d'abréviation. De plus il y a lieu de respecter la casse des noms de propres (Majuscule au nom des rues). Par exemple : Chemin et non Ch. Route et non Rte Rue de la Paix et non "rue de la paix" Etc. Exemple à ne pas reproduire Segments trop courts Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Segment_length#Too_short</nowiki> La <nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze <nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de <nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de <nowiki> </nowiki>données complètes pour ses calculs. Exemple d'un segment trop court (4m) Solution possible Vous pouvez aussi éloigner les deux nodes pour que le segment mesure au minimum 5m. La longueur d'un segment se voit en cliquant dessus puis dans le menu à gauche : <br> <br> <br> Parking Lot (Places)<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Places/Parking_lot</nowiki><br> <br> J'ai <nowiki> </nowiki>repéré pas mal d'ajouts de zones de parkings sur des places en bord de route. Celles-ci ne sont pas des aires de parking et ne devrait donc pas <nowiki> </nowiki>être cartographiées.<br> L'utilisation de ce repère est réservé aux parkings publics possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation.<br> <br> Exemple à éviter<br> <br> <br> Veillez aussi également à ne pas créer plusieurs parkings là où il y en a en fait un seul:<br> <br> <br> <br> Autres détails<br> <br> À éviter : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br> Correct : Utiliser la catégorie "Parking Lot"<br> <br> À éviter : Nommer le parking comme "Parc"; "Parking"; "P."<br> Correct : Nommer avec le nom exacte (ex. "Parking du Mont-Blanc") ou laisser le champ vide.<br> <br> <br> Parking Lot Roads<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Best_map_edi</nowiki> ... rking_Lots<br> <br> Ceci <nowiki> </nowiki>n'est qu'une liste subjective après un survol fait dans la journée. La lecture du Wiki reste primordial et pas seulement une fois. Le Wiki Suisse <nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent, ces nouveaux articles se trouvent sur le Wiki en anglais faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum daf3e403ecc70abf3b57ddd4ab5b13cda3bfd8a9 11951 11950 2017-08-04T07:45:26Z Vince1612 23 wikitext text/x-wiki (WORK IN PROGRESS!) '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' === '''Parkings et aires de stationnement''' === ==== Voies de parking ==== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire:<br>- Les entrées/sorties connectées aux routes du réseau routier<br>- Les voies qui longent le(s) commerce(s) ou bâtiment(s)<br>-<nowiki> </nowiki>Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien)<br>- Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...)<br><br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ==== Lieux (POIs) et zones de parking ==== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails'''<br>'''À éviter''' : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br>'''Correct''' : Utiliser la catégorie "Parking Lot"<br>'''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. Les voies privées (habitation) : Cartographier <nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route ne représente aucun intérêt pour la navigation et alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'au porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la <nowiki> </nowiki>bonne maison. Exemple à suivre : Exemple <nowiki> </nowiki>à ne pas suivre. Il y a énormément d'intersections ce qui augmente le risque de mauvaise manipulation d'un éditeur peu expérimenté. L'affichage sur un smartphone devient lourd et n'apporte finalement aucun intérêt pour la quasi totalité des Wazers. Demi-tours : Pour rappel, la petite flèche verte qui apparaît en fin d'une impasse ne devrait en principe jamais être mise en vert <nowiki> </nowiki>car cela veut dire que des Wazers pourront être guidés sur cette impasse pour faire demi-tour. Pour faire demi-tour si un Wazer s'est trompé, il devrait le faire au prochain giratoire, parking, ou autres mais pas dans une petite rue/impasse. Exemple d'un endroit où le demi-tour est autorisé : Source Wiki (anglais) : <nowiki>https://www.waze.com/wiki/Map_Editing_Q</nowiki> ... nd-streets Nommage : Après <nowiki> </nowiki>avoir fait un survol de la Suisse, mais plus particulièrement de la Suisse romande, je me suis rendu compte que le canton du Valais était plutôt bien cartographier mais malheureusement le nommage n'est pas très <nowiki> </nowiki>abouti. Je peux faire une grande liste de villages qui ne sont pas du tout nommés (Ville et rue) ! D'un <nowiki> </nowiki>point de vue personnel, je préfère privilégier la qualité à la quantité. A quoi bon cartographier des villages/région en entier si la majorité des segments ne sont pas localisables par leurs noms de rues et <nowiki> </nowiki>leurs noms de ville/villages ? Voici <nowiki> </nowiki>encore un exemple de pratiques d'éditions que je ne peux pas comprendre <nowiki> </nowiki>alors que nous disposons d'images aériennes de bonnes qualités depuis plusieurs mois maintenant dans une grande partie de la Suisse. Dans l'exemple ci-dessous, les éditions sont faites à la va-vite, segments tracés à l'équerre, manque le nom de la rue et de la ville. Bref, un <nowiki> </nowiki>travail de basse qualité qui n'apporte à l'heure actuelle aucun avantage pour le Wazer qui doit circuler dessus et en plus un éditeur devra grosso modo tout refaire : Cliquer pour agrandir l'image Autre <nowiki> </nowiki>petit détail, mais lors du nommage des noms de rues, il ne faut pas faire d'abréviation. De plus il y a lieu de respecter la casse des noms de propres (Majuscule au nom des rues). Par exemple : Chemin et non Ch. Route et non Rte Rue de la Paix et non "rue de la paix" Etc. Exemple à ne pas reproduire Segments trop courts Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Segment_length#Too_short</nowiki> La <nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze <nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de <nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de <nowiki> </nowiki>données complètes pour ses calculs. Exemple d'un segment trop court (4m) Solution possible Vous pouvez aussi éloigner les deux nodes pour que le segment mesure au minimum 5m. La longueur d'un segment se voit en cliquant dessus puis dans le menu à gauche : <br> <br> <br> <br> <br> <br> Parking Lot Roads<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Best_map_edi</nowiki> ... rking_Lots<br> <br> Ceci <nowiki> </nowiki>n'est qu'une liste subjective après un survol fait dans la journée. La lecture du Wiki reste primordial et pas seulement une fois. Le Wiki Suisse <nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent, ces nouveaux articles se trouvent sur le Wiki en anglais faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum 72cd2c3b29a058c141fff80e7d9810cce1ab185d 11952 11951 2017-08-04T07:54:05Z Vince1612 23 wikitext text/x-wiki (WORK IN PROGRESS!) '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' === '''Parkings et aires de stationnement''' === ==== Voies de parking ==== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ==== Lieux (POIs) et zones de parking ==== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. === '''Les voies privées (habitation)''' === Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) === '''Demi tours (U-turns)''' === Pour rappel, la petite flèche verte qui apparaît en fin d'une impasse ne devrait en principe jamais être mise en vert <nowiki> </nowiki>car cela veut dire que des Wazers pourront être guidés sur cette impasse pour faire demi-tour. Pour faire demi-tour si un Wazer s'est trompé, il devrait le faire au prochain giratoire, parking, ou autres mais pas dans une petite rue/impasse. Exemple d'un endroit où le demi-tour est autorisé : Source Wiki (anglais) : <nowiki>https://www.waze.com/wiki/Map_Editing_Q</nowiki> ... nd-streets Nommage : Après <nowiki> </nowiki>avoir fait un survol de la Suisse, mais plus particulièrement de la Suisse romande, je me suis rendu compte que le canton du Valais était plutôt bien cartographier mais malheureusement le nommage n'est pas très <nowiki> </nowiki>abouti. Je peux faire une grande liste de villages qui ne sont pas du tout nommés (Ville et rue) ! D'un <nowiki> </nowiki>point de vue personnel, je préfère privilégier la qualité à la quantité. A quoi bon cartographier des villages/région en entier si la majorité des segments ne sont pas localisables par leurs noms de rues et <nowiki> </nowiki>leurs noms de ville/villages ? Voici <nowiki> </nowiki>encore un exemple de pratiques d'éditions que je ne peux pas comprendre <nowiki> </nowiki>alors que nous disposons d'images aériennes de bonnes qualités depuis plusieurs mois maintenant dans une grande partie de la Suisse. Dans l'exemple ci-dessous, les éditions sont faites à la va-vite, segments tracés à l'équerre, manque le nom de la rue et de la ville. Bref, un <nowiki> </nowiki>travail de basse qualité qui n'apporte à l'heure actuelle aucun avantage pour le Wazer qui doit circuler dessus et en plus un éditeur devra grosso modo tout refaire : Cliquer pour agrandir l'image Autre <nowiki> </nowiki>petit détail, mais lors du nommage des noms de rues, il ne faut pas faire d'abréviation. De plus il y a lieu de respecter la casse des noms de propres (Majuscule au nom des rues). Par exemple : Chemin et non Ch. Route et non Rte Rue de la Paix et non "rue de la paix" Etc. Exemple à ne pas reproduire Segments trop courts Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Segment_length#Too_short</nowiki> La <nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze <nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de <nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de <nowiki> </nowiki>données complètes pour ses calculs. Exemple d'un segment trop court (4m) Solution possible Vous pouvez aussi éloigner les deux nodes pour que le segment mesure au minimum 5m. La longueur d'un segment se voit en cliquant dessus puis dans le menu à gauche : <br> <br> <br> <br> <br> <br> Parking Lot Roads<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Best_map_edi</nowiki> ... rking_Lots<br> <br> Ceci <nowiki> </nowiki>n'est qu'une liste subjective après un survol fait dans la journée. La lecture du Wiki reste primordial et pas seulement une fois. Le Wiki Suisse <nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent, ces nouveaux articles se trouvent sur le Wiki en anglais faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum 7e95fb710956612d88a184698ebe0ab3b9e98dde 11953 11952 2017-08-04T08:08:13Z Vince1612 23 wikitext text/x-wiki (WORK IN PROGRESS!) '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' === '''Parkings et aires de stationnement''' === ==== Voies de parking ==== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ==== Lieux (POIs) et zones de parking ==== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. === '''Les voies privées (habitation)''' === Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) === '''Demi tours (U-turns)''' === Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation. Nommage : Après <nowiki> </nowiki>avoir fait un survol de la Suisse, mais plus particulièrement de la Suisse romande, je me suis rendu compte que le canton du Valais était plutôt bien cartographier mais malheureusement le nommage n'est pas très <nowiki> </nowiki>abouti. Je peux faire une grande liste de villages qui ne sont pas du tout nommés (Ville et rue) ! D'un <nowiki> </nowiki>point de vue personnel, je préfère privilégier la qualité à la quantité. A quoi bon cartographier des villages/région en entier si la majorité des segments ne sont pas localisables par leurs noms de rues et <nowiki> </nowiki>leurs noms de ville/villages ? Voici <nowiki> </nowiki>encore un exemple de pratiques d'éditions que je ne peux pas comprendre <nowiki> </nowiki>alors que nous disposons d'images aériennes de bonnes qualités depuis plusieurs mois maintenant dans une grande partie de la Suisse. Dans l'exemple ci-dessous, les éditions sont faites à la va-vite, segments tracés à l'équerre, manque le nom de la rue et de la ville. Bref, un <nowiki> </nowiki>travail de basse qualité qui n'apporte à l'heure actuelle aucun avantage pour le Wazer qui doit circuler dessus et en plus un éditeur devra grosso modo tout refaire : Cliquer pour agrandir l'image Autre <nowiki> </nowiki>petit détail, mais lors du nommage des noms de rues, il ne faut pas faire d'abréviation. De plus il y a lieu de respecter la casse des noms de propres (Majuscule au nom des rues). Par exemple : Chemin et non Ch. Route et non Rte Rue de la Paix et non "rue de la paix" Etc. Exemple à ne pas reproduire Segments trop courts Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Segment_length#Too_short</nowiki> La <nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze <nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de <nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de <nowiki> </nowiki>données complètes pour ses calculs. Exemple d'un segment trop court (4m) Solution possible Vous pouvez aussi éloigner les deux nodes pour que le segment mesure au minimum 5m. La longueur d'un segment se voit en cliquant dessus puis dans le menu à gauche : <br> <br> <br> <br> <br> <br> Parking Lot Roads<br> Source wiki Waze : <nowiki>https://wiki.waze.com/wiki/Best_map_edi</nowiki> ... rking_Lots<br> <br> Ceci <nowiki> </nowiki>n'est qu'une liste subjective après un survol fait dans la journée. La lecture du Wiki reste primordial et pas seulement une fois. Le Wiki Suisse <nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent, ces nouveaux articles se trouvent sur le Wiki en anglais faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum a37b4d3e2d652ca61e8ec305116ca8824734e6cc 11954 11953 2017-08-04T08:22:00Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == '''Parkings et aires de stationnement''' == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == '''Les voies privées (habitations)''' == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == '''Demi tours (U-turns)''' == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation. == '''Nommage des segments''' == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == '''Segments trop courts''' == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. <br> Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. c6ae95f49ec77f03bc1633e65067baef95866045 11955 11954 2017-08-04T08:22:54Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == '''Parkings et aires de stationnement''' == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == '''Les voies privées (habitations)''' == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == '''Demi tours (U-turns)''' == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation. == '''Nommage des segments''' == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == '''Segments trop courts''' == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. <br> == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. a35a09872eb1198a0b63899f18ca8165e2622d3b 11956 11955 2017-08-04T08:24:29Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation. == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Segments trop courts == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. <br> == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 7041c04e9d351798c414a1e01df1710d509673eb 11957 11956 2017-08-04T08:25:36Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" - celle-ci est réservée aux espaces verts<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. <br> == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 7631db235756a433c98cf0a3bedfd338ac783ace 11959 11957 2017-08-04T08:32:01Z Vince1612 23 /* Lieux (POIs) et zones de parking */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre.<br>En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. <br> == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. a1576340a7b7f955bad5e7d48d6b1353f7cc8e30 11960 11959 2017-08-04T08:39:57Z Vince1612 23 /* Voies de parking */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. <br> == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 6e349505aa782a102a7eb7a9e55e22454bebbb58 0 15 11961 11915 2017-08-07T07:46:07Z Vince1612 23 /* Devenir éditeur de carte */ wikitext text/x-wiki [[Category:Suisse]] == Préambule == Waze est une application mobile de navigation pour véhicules. Waze est basé sur un système communautaire. Toutes les cartes sont créées et mises à jour par des utilisateurs de la communauté. Chacun peut apporter sa pierre à l'édifice ! Dans plusieurs pays, Waze a mis en place une carte de base créé de façon automatique. Cette base est toutefois loin d'être parfaite au niveau de la géométrie. De plus, les cartes de base ne contiennent aucune indication sur les noms des rues, noms de villes, types de routes ainsi que sur les autorisations de tourner. En Suisse, nous n'avons pas eu droit à une carte de base. Cela veut dire que toutes les routes doivent être créées par les utilisateurs (traçage, nommage, etc.). Il y a donc un travail conséquent pour obtenir une carte fiable et complète. C'est pourquoi, nous avons besoin de votre aide pour aider l'ensemble de la communauté. == Devenir éditeur de carte == Avant de faire toutes modifications sur la carte, il est nécessaire de lire la documentation en anglais ainsi que la documentation spécifique à la Suisse. Chaque pays dispose de particularité, c'est pourquoi il est nécessaire de se renseigner sur les règles propres à chaque pays. Il existe deux variantes pour éditer la carte : * Editer des routes que vous avez parcouru * Editer une région que vous connaissez Tout ceci se passe sur [https://www.waze.com/editor l'éditeur de carte Waze] (Waze Map Editor ou "WME"). === Editer des routes que vous avez parcouru === Lors de l'utilisation de l'application mobile, chacun de vos trajets est enregistré et visible dans votre tableau de bord (My Dashboard). Waze sait par conséquent chaque route que vous avez empruntée. Dès l'instant où vous avez emprunté une route, Waze vous accorde le droit d'éditer cette route sur l'éditeur de carte (WME, Waze Map Editor). Avec ce système vous êtes autorisé à modifier la géométrie, modifier les autorisations de tourner, nommer des routes, etc. Ce droit n'est toutefois pas acquis à vie, après une certaine période, Waze vous retire les droits d'éditions si vous n'avez pas réemprunté cette route dernièrement. === Editer une région que vous connaissez === Si l'édition de la carte vous plaît, vous avez la possibilité de prendre plus de responsabilité en devenant "Area Manager". En devenant Area Manager, vous n'avez plus besoin d'emprunter une route pour obtenir des droits d'éditions sur celle-ci. Vous pouvez devenir Area Manager de votre quartier, votre ville, votre canton voir plus. Pour devenir Area Manager, il faut en faire la demande en remplissant le questionnaire [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Devenir Area Manager] == Permalink == Le permalink est un lien qui se trouve en bas de l'éditeur de carte qui permet d'obtenir un lien de la zone qui est affiché sur votre écran. Ce lien peut s'avérer utile pour obtenir de l'aide sur les forums de discussions. Des informations plus complètes sont disponible sur le [[france:Waze_Map_Editor_(WME)/Zone_d'affichage_de_la_carte#Permalien|cette page]]. == Les serveurs == Waze fonctionne sur trois serveurs distincts, à savoir : * Serveur Etats-Unis, appelé plus fréquemment ''serveur NA'' * Serveur Israel, appelé plus fréquemment ''serveur IL'' * Serveur International (tous les pays sauf les USA et Israel), appelé plus fréquemment ''serveur INTL'' [[Switzerland|Retour au Wiki Suisse]] 25734546b5f329f60cadaeec80718dcab5e23432 0 18 11962 11923 2017-08-16T17:50:47Z Cedricvondk 34 /* Highways */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * Autoroute => Autoroute * Route Majeur => Semi-autoroute * Route mineur => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Rues== * <span style="color:RoyalBlue;">'''Rue Primaire'''</span> => Route principale * Rue => Toutes les autres rues, rues secondaires, etc. * <span style="color:RoyalBlue;">'''Service Road'''</span> => Route d'accès à des services ( essence, restaurant, magasin, Mc Do, etc). ==Other - drivable== * <span style="color:RoyalBlue;">'''Dirt Roads/4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Parking Lot Road'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non-drivable== * <span style="color:RoyalBlue;">'''Walking Trails'''</span> => Chemin pédestre * <span style="color:RoyalBlue;">'''Pedestrian Boardwalk'''</span> => Zone piétonne, bords de lac * <span style="color:RoyalBlue;">'''Stairway'''</span> => Escalier * <span style="color:RoyalBlue;">'''Railroad'''</span> => Chemin de fer * <span style="color:RoyalBlue;">'''Runway/Taxiway'''</span> => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseilé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principale <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] 1642d3e9e341cab9b4b7d00bc4076a88aae06c27 11963 11962 2017-08-16T17:57:26Z Vince1612 23 wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Highways== * <span style="color:RoyalBlue;">'''Freeway'''</span> => Autoroute * <span style="color:RoyalBlue;">'''Major Highway'''</span> => Semi-autoroute * <span style="color:RoyalBlue;">'''Minor Highway'''</span> => Route nationale et principale * <span style="color:RoyalBlue;">'''Ramps'''</span> => Entrées et sorties d'autoroutes ==Streets== * <span style="color:RoyalBlue;">'''Primary Street'''</span> => Route principale * <span style="color:RoyalBlue;">'''Street'''</span> => Toutes les autres rues, rues secondaires, etc. * <span style="color:RoyalBlue;">'''Service Road'''</span> => Route d'accès à des services ( essence, restaurant, magasin, Mc Do, etc). ==Other - drivable== * <span style="color:RoyalBlue;">'''Dirt Roads/4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Parking Lot Road'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non-drivable== * <span style="color:RoyalBlue;">'''Walking Trails'''</span> => Chemin pédestre * <span style="color:RoyalBlue;">'''Pedestrian Boardwalk'''</span> => Zone piétonne, bords de lac * <span style="color:RoyalBlue;">'''Stairway'''</span> => Escalier * <span style="color:RoyalBlue;">'''Railroad'''</span> => Chemin de fer * <span style="color:RoyalBlue;">'''Runway/Taxiway'''</span> => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseilé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principale <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] bb4489d4ea2c5a76516890d62c76fee68c098bbd 11964 11963 2017-08-16T18:04:09Z Cedricvondk 34 /* Highways */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * '''Autoroute''' => Autoroute * '''Route Majeur''' => Semi-autoroute * '''Route Mineure''' => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Streets== * <span style="color:RoyalBlue;">'''Primary Street'''</span> => Route principale * <span style="color:RoyalBlue;">'''Street'''</span> => Toutes les autres rues, rues secondaires, etc. * <span style="color:RoyalBlue;">'''Service Road'''</span> => Route d'accès à des services ( essence, restaurant, magasin, Mc Do, etc). ==Other - drivable== * <span style="color:RoyalBlue;">'''Dirt Roads/4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Parking Lot Road'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non-drivable== * <span style="color:RoyalBlue;">'''Walking Trails'''</span> => Chemin pédestre * <span style="color:RoyalBlue;">'''Pedestrian Boardwalk'''</span> => Zone piétonne, bords de lac * <span style="color:RoyalBlue;">'''Stairway'''</span> => Escalier * <span style="color:RoyalBlue;">'''Railroad'''</span> => Chemin de fer * <span style="color:RoyalBlue;">'''Runway/Taxiway'''</span> => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseilé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principale <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] 22ff5dca02ecf62c4ee4bb16d20b2096cd685973 11965 11964 2017-08-16T18:11:30Z Cedricvondk 34 /* Streets */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * '''Autoroute''' => Autoroute * '''Route Majeur''' => Semi-autoroute * '''Route Mineure''' => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Rues== * '''Rue Primaire''' => Route principale * '''Rue''' => Toutes les autres rues, rues secondaires, etc. ==Autres Carrossables== * <span style="color:RoyalBlue;">'''Chemin de terre / 4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Air de Stationnement'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations, accès aux stations service, etc. * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non carrossables== * <span style="color:RoyalBlue;">'''Walking Trails'''</span> => Chemin pédestre * <span style="color:RoyalBlue;">'''Pedestrian Boardwalk'''</span> => Zone piétonne, bords de lac * <span style="color:RoyalBlue;">'''Stairway'''</span> => Escalier * <span style="color:RoyalBlue;">'''Railroad'''</span> => Chemin de fer * <span style="color:RoyalBlue;">'''Runway/Taxiway'''</span> => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseilé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principale <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] ce904f9aac3071c7e32711c2ec3866c99dde7fca 11966 11965 2017-08-16T18:17:18Z Cedricvondk 34 /* Non carrossables */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * '''Autoroute''' => Autoroute * '''Route Majeur''' => Semi-autoroute * '''Route Mineure''' => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Rues== * '''Rue Primaire''' => Route principale * '''Rue''' => Toutes les autres rues, rues secondaires, etc. ==Autres Carrossables== * <span style="color:RoyalBlue;">'''Chemin de terre / 4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Air de Stationnement'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations, accès aux stations service, etc. * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non carrossables== * <span style="color:RoyalBlue;">'''Chemin piéton routable'''</span> => Chemin pédestre * Chemin piéton non routable => Zone piétonne, bords de lac * Escaliers => Escalier * Voie ferrée => Chemin de fer * Piste aéroport => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un point ou une zone "Airport"!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principale <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] 9bf018678084458770e2ea7752c1bdc59cab9746 11967 11966 2017-08-16T18:18:48Z Cedricvondk 34 /* Non carrossables */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * '''Autoroute''' => Autoroute * '''Route Majeur''' => Semi-autoroute * '''Route Mineure''' => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Rues== * '''Rue Primaire''' => Route principale * '''Rue''' => Toutes les autres rues, rues secondaires, etc. ==Autres Carrossables== * <span style="color:RoyalBlue;">'''Chemin de terre / 4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Air de Stationnement'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations, accès aux stations service, etc. * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non carrossables== * <span style="color:RoyalBlue;">'''Chemin piéton routable'''</span> => Chemin pédestre * '''Chemin piéton non routable''' => Zone piétonne, bords de lac * '''Escaliers''' => Escalier * '''Voie ferrée''' => Chemin de fer * '''Piste aéroport''' => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un point ou une zone "Airport"!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Primary Street ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Street =Nommage des routes= ==Autoroute== Freeway => Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Major Highway => Semi-autoroute * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Minor Highway => Route nationale et principale <br> * Nommage en ville: Avec nom de la rue et "Alt Street/Alias" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Primary Street => Route principale <br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Ramps => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). * Sortie Zürich Flughafen, Sortie Bülach-Nord * Entrée > Basel Bern Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Entrée > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une zone "Landmark" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Junction/Interchange". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] f4ec71237b34cdcf3b735bb9c2c06da281102c38 11968 11967 2017-08-16T18:33:27Z Cedricvondk 34 /* Les panneaux */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * '''Autoroute / Semi-Autoroute''' => Autoroute * '''Route Majeur''' => Semi-autoroute * '''Route Mineure''' => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Rues== * '''Rue Primaire''' => Route principale * '''Rue''' => Toutes les autres rues, rues secondaires, etc. ==Autres Carrossables== * <span style="color:RoyalBlue;">'''Chemin de terre / 4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Air de Stationnement'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations, accès aux stations service, etc. * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non carrossables== * <span style="color:RoyalBlue;">'''Chemin piéton routable'''</span> => Chemin pédestre * '''Chemin piéton non routable''' => Zone piétonne, bords de lac * '''Escaliers''' => Escalier * '''Voie ferrée''' => Chemin de fer * '''Piste aéroport''' => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un point ou une zone "Airport"!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Rue Primaire ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Rue =Nommage des routes= ==Autoroute== Autoroute / Semi-Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Route Majeure * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Route Mineure * Nommage en ville: Avec nom de la rue et "Ajouter un nom différent" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Rue Primaire<br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Rampe => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). Le signe / sert a séprarer les villes et fait 0.25 seconde de pause dans la prononciation. * Sortie > Zürich / Flughafen, Sortie Bülach-Nord * A1 > Basel / Bern / Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une "Zone" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Jonction/Échangeur". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] f4f9df3efce4e73dab8430c00590a68c9848b357 0 7 11969 10478 2017-08-16T18:40:06Z Cedricvondk 34 /* Straßen */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. * Ausfahrt Zürich Flughafen, Ausfahrt Bülach-Nord * Einfahrt > Basel Bern Luzern, Einfahrt > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt Niederbipp Langenthal *[[Image:WegweiserAutobahn.png]] Einfahrt > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Sie dürfen keine Verbindung zu existierenden Strassen haben und sollen mit Level -5 versehen werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 5 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 1a923a536532fbca9354e4c29333a7ddb59d6f05 11973 11969 2017-08-17T09:36:23Z Cedricvondk 34 /* Ein- und Ausfahrten */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt Zürich / Flughafen, Ausfahrt Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Sie dürfen keine Verbindung zu existierenden Strassen haben und sollen mit Level -5 versehen werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 5 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] e8f418faef8d4ee14a2838b084d9fcdbf8e00ee6 11975 11973 2017-08-17T14:39:22Z Cedricvondk 34 /* Ein- und Ausfahrten */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Sie dürfen keine Verbindung zu existierenden Strassen haben und sollen mit Level -5 versehen werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 5 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 9f5dd9d24430d3098b82006c5ac346249be7232f 0 17 11974 10937 2017-08-17T10:45:10Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] 3782e8d61d70f72023ab8d3cfd44a33c1427ca78 0 79 11976 2017-08-17T18:23:56Z Cedricvondk 34 Die Seite wurde neu angelegt: «== Guide des instructions de guidage ==» wikitext text/x-wiki == Guide des instructions de guidage == f39d09f83b7bad5e84796b4f25580a453478699e 0 18 11977 11968 2017-08-20T09:27:27Z Cedricvondk 34 /* Entrées et sorties */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * '''Autoroute / Semi-Autoroute''' => Autoroute * '''Route Majeur''' => Semi-autoroute * '''Route Mineure''' => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Rues== * '''Rue Primaire''' => Route principale * '''Rue''' => Toutes les autres rues, rues secondaires, etc. ==Autres Carrossables== * <span style="color:RoyalBlue;">'''Chemin de terre / 4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Air de Stationnement'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations, accès aux stations service, etc. * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé ==Non carrossables== * <span style="color:RoyalBlue;">'''Chemin piéton routable'''</span> => Chemin pédestre * '''Chemin piéton non routable''' => Zone piétonne, bords de lac * '''Escaliers''' => Escalier * '''Voie ferrée''' => Chemin de fer * '''Piste aéroport''' => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un point ou une zone "Airport"!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Rue Primaire ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Rue =Nommage des routes= ==Autoroute== Autoroute / Semi-Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Route Majeure * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Route Mineure * Nommage en ville: Avec nom de la rue et "Ajouter un nom différent" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Rue Primaire<br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Rampe => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). Le signe / sert a séparer les villes et fait 0.25 seconde de pause dans la prononciation. * Sortie 10 > Zürich / Flughafen, Sortie 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une "Zone" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Jonction/Échangeur". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] 3a1d2c081db2263ceecc2336ff2d67c4b0c9421e 11978 11977 2017-08-20T09:28:54Z Cedricvondk 34 /* Autres Carrossables */ wikitext text/x-wiki [[Switzerland|Retour au Wiki Suisse]] =Classification des routes= Ici vous trouvez les informations sur : comment nommer les routes et les villes en Suisse. * Pour les questions vous êtes invité à participer à la discussion sur le forum Switzerland [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. =Légende de la Carte Suisse= Voilà la [[Légende de la Carte Suisse]] avec informations sur les panneaux et les segments. =Les categories des routes= ==Routes== * '''Autoroute / Semi-Autoroute''' => Autoroute * '''Route Majeur''' => Semi-autoroute * '''Route Mineure''' => Route nationale et principale * <span style="color:RoyalBlue;">'''Rampe'''</span> => Entrées et sorties d'autoroutes ==Rues== * '''Rue Primaire''' => Route principale * '''Rue''' => Toutes les autres rues, rues secondaires, etc. ==Autres Carrossables== * <span style="color:RoyalBlue;">'''Chemin de terre / 4x4 Trails'''</span> => route non goudronnée, route de forêt, route pour tracteur/4/4 * <span style="color:RoyalBlue;">'''Air de Stationnement'''</span> => Grandes aires de stationnement le long des (auto)routes ou dans les agglomérations, accès aux stations service, etc. * <span style="color:RoyalBlue;">'''Private Road'''</span> => Chemin privé (accès aux riverains, trafic agricole) ==Non carrossables== * <span style="color:RoyalBlue;">'''Chemin piéton routable'''</span> => Chemin pédestre * '''Chemin piéton non routable''' => Zone piétonne, bords de lac * '''Escaliers''' => Escalier * '''Voie ferrée''' => Chemin de fer * '''Piste aéroport''' => Piste d'atterrissage <br>(C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un point ou une zone "Airport"!) ==Les panneaux== La classification des routes principales et secondaires: * Il faut suivre le panneau qu'on trouve sur la rue. ** Panneau bleu, panneau d'entrée de village bleu, signal route principale (carré jaune) => Rue Primaire ** Panneau blanc, panneau d'entrée de village blanc (route secondaire) => Rue =Nommage des routes= ==Autoroute== Autoroute / Semi-Autoroute * Nommage A1, A2 etc. ==Semi-autoroute== Route Majeure * Nommage A1L, A52 etc. ==Routes nationales (numéro 1-30)== Route Mineure * Nommage en ville: Avec nom de la rue et "Ajouter un nom différent" N1, N2 etc. * Nommage hors ville: Sans nom de la rue, seulement N1, N2 etc. ==Routes principales numérotés== Rue Primaire<br> * Nommage en ville: Avec nom de la rue * Nommage hors ville: Sans nom de la rue ==Entrées et sorties== Rampe => Entrée et sortie de l'autoroute ou semi-autoroute, nommage selon les panneaux d'Entrée et sortie. Les villes donnent en même temps la direction. Pour une bonne direction dans l'entrée on utilise le signe ">" qui signifie direction et qui et prononcé avec TTS (Text-to-Speech). Le signe / sert a séparer les villes et fait 0.25 seconde de pause dans la prononciation. * Sortie 10 > Zürich / Flughafen, Sortie 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, Entrée > Zürich Dietikon *[[Image:AusfahrtWegweiser.png]] Sortie 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Nommage des entrées, sorties et des embranchements d'autoroutes=== Nous mettons une "Zone" sur les entrées, sorties et les embranchements d'autoroutes. La zone est adaptée aux entrées et sorties et nommée avec un nom et le numéro de l'embranchement. Comme type on choisit "Jonction/Échangeur". '''Exemple:''' "17 Frick" *[[Image:Frick.png|600px]] '''Exemple:''' "8 Liestal" *[[Image:Augst.png|600px]] =Nommage des villes et villages= Retrouvez ici [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] Attention, seuls les noms de villes mentionnés dans [http://www.waze.com/wiki/index.php?title=Ortsliste_Schweiz liste des villes de Suisse] doivent être utilisés. =Informations importantes= ==Rue forestière== Attention : sur certaines rues forestières, seuls les piétons sont autorisés. ==Chemin de fer== En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ==Les voies== En général, il y a deux voies pour les autoroutes. Cela facilite le mapping (édition de la carte) des entrées et sorties. * Pour les autres rues: s'il y a suffisamment de place entre les voies (selon wiki 5 mètres) ou s'il y a des points GPS bien séparés dans l'éditeur au zoom de 100m, on peut mettre deux voies pour les routes nationales et principales. =Sources= *Liste de communes en Suisse [http://fr.wikipedia.org/wiki/Liste_des_communes_de_Suisse] *Liste des autoroutes de Suisse [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] *Liste des semi-autoroutes (Major Highway, seulement en allemand) [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste des routes nationales (Freeways/Minor Highways) [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste des routes principales numérotés (1-30:minor highway, >30:primary street)[http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Retour au Wiki Suisse]] [[Category:Suisse]] fa57b05bec51b10edf41a5d5cb28160a61565825 0 17 11979 11974 2017-08-20T09:54:19Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[Image:Routes_Autoroute.png|200px]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] c64b371233b75a14513cec37708869da4c5fe4f0 11980 11979 2017-08-20T10:01:00Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[Image:Routes_Autoroute.png|200px]]''' <gallery> Routes_Autoroute.png|Autoroute </gallery> Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] f5f298eb17aeb61646aa43a88121aa90632d976d 11981 11980 2017-08-20T10:05:52Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[Image:Routes_Autoroute.png|200px]]''' [[File:Routes_Autoroute.png]] Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] e86850d5013f75f9ed0c2077b9adbe86f99f55c8 11982 11981 2017-08-20T10:09:42Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[Image:Routes Autoroute.png|200px]]''' [[File:Routes_Autoroute.png]] Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] afc5ef95866308169a08a72c2107920f663fe01b 11983 11982 2017-08-20T10:11:39Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[File:Routes_Autoroute.png|200px]]''' [[File:Routes_Autoroute.png]] Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] be6a2d3720786c1916296d683f87c00b132e52f4 11984 11983 2017-08-20T10:12:20Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[File:Routes_Autoroute.png]]''' [[File:Routes_Autoroute.png]] Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] 8df14e9a9b38ed589da38bc9a23cb194fffb7c53 11985 11984 2017-08-20T10:13:18Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Highways=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[Image:Routes Autoroute.PNG]]''' [[File:Routes_Autoroute.png]] Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] 23218106d3510fc299457c2bec5dffa9a418bc91 11986 11985 2017-08-20T10:16:19Z Cedricvondk 34 /* Types des segments */ wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Routes=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[Image:Routes Autoroute.PNG]]''' [[File:Routes_Autoroute.png]] Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] a4fffb0ba52946c6189674a8375f7ba8a30c2930 11987 11986 2017-08-20T10:17:09Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Routes=== '''Freeway [[Image:RoadBlue.png|200px]]''' '''Autoroute [[Image:Routes Autoroute.PNG]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] 74848d1f0bf13c7ee34d811be86f481ea11ad31f 11988 11987 2017-08-20T10:49:38Z Cedricvondk 34 wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Routes=== '''Autoroute [[Image:RoadBlue.png|200px]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- '''Service Road [[Image:Service road.png|200px]]''' Les Service Roads sont les routes de station d'essence, les parking sur autoroute ou les drive-ins. [[Image:RoadPicN5b.jpg|400px]] ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] c4eb8c2d55221995f5b2fca52d35ddd016467723 11989 11988 2017-08-27T10:35:38Z Cedricvondk 34 /* Streets */ wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Routes=== '''Autoroute [[Image:RoadBlue.png|200px]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- '''Railroad [[Image:Service road.png|200px]]''' Railroad sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires ne doivent pas avoir de connection avec d'autres rues et le niveau (Level) doit être à -5. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] 9fe226e9c63f3230f10e1d832d7a56d83bcd79ee 11991 11989 2017-09-14T09:53:49Z Cedricvondk 34 /* Types des segments */ wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Routes=== '''Autoroute [[Image:RoadBlue.png|200px]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- Voie ferrée ''' [[Image:Service road.png|200px]]''' Voie ferrée sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires peuvent être connectées avec d'autres rues pour les passages à niveau. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] cd3d483de4fad31d57ad747c5b4a87c792e50e17 11993 11991 2017-09-14T11:23:11Z Cedricvondk 34 /* Types des segments */ wikitext text/x-wiki [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] ==Segments et croisements== [[Image:Segment croisement.png]] '''Qu'est-ce qu'un segment?''' Un segment est une ligne, limitée par deux points. Dans [[Der Waze Map-Editor|Waze Map-Editor]], nous utilisons des [[Erstellen und bearbeiten eines Segments|segments]] pour dessiner de nouvelles rues. Comme expliqué ci-dessus, un segment est limité, dans notre cas, par un [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|croisement]]. <b>Il est important de noter que la classification des routes est différente dans chaque pays. Il est donc très important, avant de commencer l'édition dans un pays étranger, de lire le Wiki national du pays</b> ==Types des segments== ===Routes=== '''Autoroute [[Image:RoadBlue.png|200px]]''' Un Freeway est une autoroute avec voies séparées, sans feux et sans panneau de stop. Les autoroutes sont uniquement accessibles par les entrées et sorties. Les autres rues ne doivent pas être connectées à une autoroute. Les exceptions sont les voies de services de secours. Beaucoup de routes nationales suivent des autoroutes. Dans ce cas, la signalisation de l'autoroute est prioritaire. Voici une liste de toutes les autoroutes en Suisse: [http://fr.wikipedia.org/wiki/Liste_des_autoroutes_de_Suisse] La couleur des panneaux des autoroutes en Suisse est verte. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Major Highway [[Image:Majorhighwayseg.png |200px]]''' Un Major Highway est une semi-autoroute. Voici la liste des semi-autoroutes (Major Highway, seulement en allemand): [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] La couleur des panneaux des semi-autoroutes en Suisse est verte. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Minor Highway [[Image:RoadYell.png |200px]]'''<br> Un Minor Highway est une route nationale. Toutes les autres routes jaunes sont classées comme Primary Street (route principale). Voici la liste des routes principales numérotées: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Ramp [[Image:Ramp.png |200px]]''' Les rampes sont utilisées pour les entrées et sorties sur autoroute et semi-autoroute. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Streets=== Dans les villes et villages on trouve des types de route différents: ---- '''Primary Street [[Image:Primary street.png|200px]]''' Les Primary Street correspondent aux panneaux de signalisation suivants : [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Street [[Image:Street.png|200px]]''' Comme Street nous nommons toutes les routes secondaires et routes de quartiers, qui sont accessibles à la circulation normal. Ces routes peuvent être à sens unique ou à deux-sens. Les routes secondaires sont affichées avec des panneaux blancs [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Route normale: [[Image:RoadPicN4.jpg|400px]] ---- ---- '''Dirt Roads / 4x4 Trails [[Image:Service road.png|200px]]''' Dirt Roads sont les routes non goudronée, routes de forêt, routes pour tracteur et 4x4 [[Image:RoadPicN6.jpg |400px]] ---- '''Parking Lot Road [[Image:Service road.png|200px]]''' Parking Lot Road sont les grands parking, parking de restauroute, routes des parking ou lieux avec parking, accès aux stations-service. [[Image:RoadPicN7.jpg |400px]] ---- '''Private Road [[Image:Service road.png|200px]]''' Private Road sont tous les rues privés qui sont affichés comme rue privé. ---- '''Walking Trail [[Image:Service road.png|200px]]''' Walking Trail sont tous les chemins pédestre [[Image:RoadPicN9.jpg |400px]] ---- '''Pedestrian Boardwalk[[Image:Service road.png|200px]]''' Pedestrian Boardwalk sont tous les zones piétonnes et zones piétonnes aux bords des lac [[Image:RoadPicN10.jpg|400px]] ---- '''Stairway [[Image:Service road.png|200px]]''' Stairway sont les escaliers. [[Image:RoadPicN11.jpg|400px]] ---- Voie ferrée ''' [[Image:Service road.png|200px]]''' Voie ferrée sont les chemins de fer. En général on ne devrait pas enregistrer les voies ferroviaires avec le client, mais plutôt dans l'éditeur. Les voies ferroviaires peuvent être connectées avec d'autres rues pour les passages à niveau. Spécifier le nom de la compagnie en tant que Nom de Rue et aucune ville. Verrouiller en Level 2. ---- '''Runway/Taxiway [[Image:Service road.png|200px]]''' Runway/Taxiway peuvent être les pistes d'attérissages. C'est pour compléter la carte. Il n'est pas conseillé de mettre tous les aéroports. Il suffit de mettre un landmark (Airport)! <br> [[Comment nommer les routes et les villes en Suisse|Retour à Comment nommer les routes et les villes en Suisse]] [[Category:Suisse]] e865c3b01a6e0a62f1aafbd9337fc493250cadfe 0 13 11990 10791 2017-09-07T13:34:12Z BellHouse 29 /* Anmeldung Area-Manager */ AMS DE -BellHouse +Jerec35 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für den AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' * Für die Wazer in seiner Region im '''Forum''' verfügbar sein. * Den Editoren seiner Gegend Hilfestellung leisten. * Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' * '''Update-Requests''' bearbeiten. * '''Map-Problems''' bearbeiten. * '''Blitzer''' überprüfen. == Anmeldung Area-Manager == Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Schon recht sattelfest in den Editier-Regeln sein *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:''' *Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. *Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. *Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. *Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. *Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. *Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". *Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. *Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für alle DACH-Länder:''' *Snake68 (D) *Jerec35 (D) *TSWA (AT) *GPSRitter (AT) *Caradellino (AT) *popel22 (CH) *svx-biker (CH) *pjw65 (CH) === Richtlinien, die Du genau kennen solltest! === '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. === Online-Formular === Folgendes musst Du tun: *Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. *Klicke auf [[WME Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. *Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. *Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: * [https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] * Österreich (kommt bald) * Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] c93b4c0a29b657924a70195ae7a2215b2b74a272 0 7 11992 11975 2017-09-14T11:20:13Z Cedricvondk 34 /* Eisenbahnen */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Eisenbahnlinien können bei niveaugleichen Bahnübergängen mit anderen Strassen verbunden werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 2 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] dbfb031f2718a842b34f86666dd9af041efc7295 0 78 11994 11960 2017-09-28T07:16:06Z Vince1612 23 Ajout Boucles et Culs-de-sac wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === <br>Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les supprimes, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" (FR: segments avec nœuds de fin identiques") ou "same connection segments" (FR: segment avec la même connexion). Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par un rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. ce3d02d66b0ffa383f0a3041cda064c9ff3a5c82 11995 11994 2017-09-28T07:18:49Z Vince1612 23 typo wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === <br>Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" (FR: segments avec nœuds de fin identiques") ou "same connection segments" (FR: segment avec la même connexion). Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par un rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 1f477c71d6de3715c15f0a5a3f8dc470f7fc2c70 11996 11995 2017-09-28T07:23:07Z Vince1612 23 /* Segments trop courts */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === <br>Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" (FR: segments avec nœuds de fin identiques") ou "same connection segments" (FR: segment avec la même connexion). Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par un rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. e49866e807be1300a509298eab9db1d362ea7a8b 11997 11996 2017-09-28T07:28:47Z Vince1612 23 removed unnecessary space wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" (FR: segments avec nœuds de fin identiques") ou "same connection segments" (FR: segment avec la même connexion). Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par un rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 0ce42448cdb49d4180f13102af758af028d815aa 11998 11997 2017-09-28T07:43:28Z Vince1612 23 italique pour 2 phrases wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par un rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 0f4ec14af9d83e60729536b563498be4c3bcb4e6 0 1 11999 11943 2017-10-29T20:18:26Z Popel22 24 Die Client Anleitung war veraltet. Habe das Help Center verlinkt wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone]. Hilfe findest Du [[hier]] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] f2b90ca7a5a52dc7c95af726cfd9fac9aa55fcf7 12000 11999 2017-10-29T20:23:40Z Popel22 24 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone]. Hilfe und Anleitungen findest Du (vorerst nur auf englicsh im [https://support.google.com/waze#topic=6273402 Help Center] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] b94f539e036ad4da8a98eabb32cc3c11f5eb54e9 12001 12000 2017-10-29T20:24:12Z Popel22 24 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone]. Hilfe und Anleitungen findest Du (vorerst nur auf englisch im [https://support.google.com/waze#topic=6273402 Help Center] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] f12abeee117c9ef4feb787e712418647cfa83231 0 80 12002 2017-10-29T20:28:30Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Diese Seite über die häufig gestellten Fragen in Waze sollte mit dem [http://www.waze.com/faq/ Of…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Diese Seite über die häufig gestellten Fragen in Waze sollte mit dem [http://www.waze.com/faq/ Official FAQ] und dem [http://www.waze.com/faq/technical_faq/ Technical FAQ] gelesen werden. Der [[Glossar|Glossar]] erklärt die Begriffe und die speziellen Bezeichnungen in Waze. =WME - Karteneditor= === Welche Browser werden vom Waze Map-Editor unterstützt? === Waze empfiehlt [http://www.google.com/chrome Google Chrome] Browser oder das [http://www.google.com/chromeframe Google Chrome Frame] Plugin mit dem Internet Explorer zu verwenden. Die Unterstützung für Microsoft Internet Explorer (IE) ist limitiert und manche Funktionen arbeiten evtl. nicht korrekt. Folgende Browser funktionieren mit dem Waze Map-Editor: *[http://www.google.com/chrome Chrome] (Empfohlen) *[http://www.apple.com/safari Safari] *[http://www.mozilla-europe.org/nl/firefox Firefox] === Was ist die Base-Map? === Die Base-Map ist eine Basis-Karte, die von Waze implementiert wurde. Die Base-Map ist in ihrer Rohform komplett unbearbeitet, das heisst: Es sind nur Straßen vorhanden und keine Straßen- oder Ortsnamen. Die Karte ist schlecht navigierbar und in der Regel müssen alle Straßen auch in ihrer Klassifizierung überprüft werden. Einbahnstraßen sind inexistent und auch alle Abbiegungen müssen erst noch gesetzt werden, bevor eine saubere Navigation möglich ist. Die Base-Map Straßen haben auch alle keine Fahrtrichtung. Deutschland ist beispielsweise ein Base-Map Land. === Wieso sind die Satellitenbilder inexistent oder in schlechter Auflösung? === Aufgrund des Geschäftsmodells, welches die Anwendung kostenlos für die Benutzer hält, ist man limitiert in den Quellen. Waze bezieht die Luftbilder von Bing. Waze verwendet keine anderen kommerziellen Quellen. Wenn man alte oder schlechte Bilder vorfindet kann man dies mit diesem [https://docs.google.com/a/waze.com/spreadsheet/viewform?hl=en_US&formkey=dDFhcGpGNGdWWmRiTXMxa2tOS2RlYWc6MQ#gid=0 Formular] melden. === Was ist der Waze Map-Editor? === Der Waze Map-Editor oder "WME" (interner Code Name Papyrus) ist der Name des neuen Karteneditors.<br> Man kann sich anmelden unter:<br> https://www.waze.com/de/editor/ === Was sind Fahrten (Drives)? === "Drives" sind die Fahrten, die Du mit eingeschaltener Waze-App gemacht hast. Während der Fahrt speichert Waze die gefahrene Strecke (Ort, Zeit und Geschwindigkeiten) und überträgt diese Infos an den Server. Diese Daten validieren den bestehenden Zustand der Karte, lernen durchschnittliche Fahrzeiten ein (sogen. Segmentgeschwindigkeitsdaten) und lernen den Wazeservern gebräuchliche Wege. Die Benutzer oder Area-Manager, welche die Karte bearbeiten, können im Karteneditor die gefahrenen Strecken anhand anonymisierter GPS-Punkte sehen und die Straßen auf der Karte wenn nötig einzeichnen oder im Verlauf anpassen. Jeder Benutzer kann seine eigenen Fahrten unter "Fahrten" im Karteneditor anschauen. === Wann sehe ich meine Fahrten im Karteneditor? === Die Fahrten sind nach etwa einer Stunde im Waze Map-Editor sichtbar. Kurze Fahrten unter 50 Kilometer sind meist in weniger als 15 Minuten im Waze Map-Editor. Wenn die Server Probleme haben oder die Fahrten länger als 150 Kilometer sind, kann es sein, dass es bis zu einer Woche dauert. Sind die Fahrten nach einer Woche nicht vorhanden, sollte man dies via [https://world.waze.com/support/ Quick Help] auf der Support-Seite melden. Benutze den Mail-Link und beschreibe Dein Problem. Ein Blick auf die [http://status.waze.com/ Status Seite] oder ins [http://world.waze.com/forum Forum] kann auch hilfreich sein. === Was ist eine gesperrte Straße im Waze Map-Editor? (Lock)=== Die "Sperren" Funktion bewirkt folgendes: Ein gesperrtes Segment kann nicht durch Editoren mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]] bearbeitet werden. Der Rang eines Editors ermöglicht Ihm ein Segment mit einer "Bearbeitungssperre" (Lock) auf maximal seinem Editorenlevel zu versehen. Sinnvoll ist dies als Schutz bei wichtigen Hauptverkehrsadern wie Autobahnen (Freeway - Locklevel 5) oder Bundesstraßen (Locklevel 3). Gesperrte Segmente beeinflussen die Abbiegungen der Kreuzungen an den Enden der Segmente. Wenn eine Abiegung nicht geändert werden kann, ist möglicherweise ein Segment an der Kreuzung gesperrt. Zum entsperren der Segmente, richtet man eine Anfrage an das betreffende Forum. Es gibt Threads zum Thema Entsperren von Straßen.. Ausserdem kann oft ein L5/L6-Editor im Chat weiter helfen. Lies zum Thema "Sperren von Straßen" diese [[Sperren von Straßen (Locking)|Seite]]. ===Was ist das Penalty-System=== Für die Erstellung einer Route verwendet Waze unter anderem ein System von Penalties (Zeitzuschlägen). Das Penalty-System ist dafür verantwortlich, den schnellsten Weg zu finden. Es eliminiert mögliche Routen indem es für die Berechnung mehr Zeit (pro Segment oder Kreuzung) vergibt als erwartet.<br> Infos in deutscher Sprache findest Du auf dieser Seite: [[Wie Waze Routen kalkuliert]]<br> Infos in Englisch findest Du auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. Gib in unter "Stell eine Frage" der nanoRep Box das Wort "Penalties" ein.<br> ===Unterstützt Waze zeitlich begrenze Abbiegeverbote?=== Ja, Informationen dazu findest Du hier: [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] =Waze-App= === Was bedeuten die kleinen Punkte auf den Straßen? === Dies sind Straßen, die noch nicht bestätigt wurden. Das heisst, dass diese Straßen noch nie befahren wurden, seit sie mit dem Karteneditor erstellt oder mit der Basis-Karte importiert wurden. Es kann sein, dass die Kreuzungen und die Geometrie nicht zu 100% korrekt sind, daher sollte man diesen Straßen Beachtung schenken. Wenn über solche Straßen gefahren wird, ändert sich das Waze-Icon auf dem Bildschirm und zeigt einen Pacman an der die Punkte verspeist. Dies gibt Punkte und bestätigt die Straße für Waze. Diese Straßen werden auch oft [[Glossar#Pacman_Roads.2C_Pacman_Stra.C3.9Fen|Pacman-Straßen]] genannt. Mehr dazu [[Ablauf_der_Aktualisierungsprozesse#Punkte_fressen.28Munching.2FPacman-Roads.29|hier]]. Die Punkte erhält nur, wer die Straße als erstes mit dem Pacman befährt. Die Straßen können noch länger unbestätigt erscheinen. === Was ist, wenn man beim Fahren keine Straße in der App sieht? === Wenn eine Straße befahren wird, die nicht in der App sichtbar ist, speichert Waze zwar die Routeninformationen wie gewohnt, fügt aber die Straße nicht ohne weiteres zum Karteneditor oder der Live Map hinzu. In diesem Fall kann man die Straße über die App [[Zeichne Straße auf |aufzeichnen]]. Die aufgezeichnete Straße erscheint rot in Waze und setzt auch an verschiedenen Stellen Kreuzungen, wo Waze z.B. eine Abbiegung während der Fahrt entdeckt. Wenn Waze wieder zurück auf eine vorhandene Straße kommt, sollte die Aufnahme automatisch pausieren. Man sollte diese Funktion nur verwenden, wenn auf Straßen gefahren wird, die noch nicht auf der Karte existieren! Waze zeichnet bei ungenauem GPS-Signal Straßen auf, wo schon welche vorhanden sind, da die Anwendung in diesem Fall der Meinung ist, dass man sich nicht auf einer existierenden Straße befindet. Dies führt zu unerwünschten Korrekturen durch die Editoren oder Area-Manager. Es ist auch zu beachten, dass Waze bei fehlender oder schlechter Netz-Abdeckung die Karte nicht in die Anwendung herunterladen kann. Das heisst: es ist keine Karte sichtbar, aber sie ist trotzdem bereits vorhanden. Auch in diesem Moment können Straßen aufgezeichnet werden. Daher Vorsicht bei der Aufzeichnung! === Ich habe neue Straßen aufgezeichnet - was nun? === Die neu aufgezeichneten Straßen erscheinen innerhalb kurzer Zeit im Karteneditor, wo Du diese weiter bearbeiten kannst. Bitte erledige dies innerhalb kurzer Frist, sonst wird die Karte nicht erweitert und die Benutzer können nicht von deiner Arbeit profitieren. Melde Dich dazu im Karteneditor an und bearbeite die Straßen. Details wie Straßenname, Stadt-/Gemeindename, Fahrtrichtungen, Straßentyp usw. sollten alle im Karteneditor ergänzt werden. Dabei sollte man die neue Straße mit bereits bestehenden verbinden und die Abbiegeverbote korrekt setzen. Ansonsten kann die Straße nicht oder nicht richtig bei der Navigation berücksichtigt werden. === Wann sehe ich meine Straßen in der Waze-App? === Das normale Verfahren ist, dass in regelmäßigen Abständen ein Aktualisierungsprozess auf den Servern ausgeführt wird (Stand 2016: 1-3x pro Woche). Wenn er beginnt, werden alle Edits bis zu diesem Zeitpunkt in den aktuellen Karten-Aktualisierungszyklus aufgenommen. Nachdem Aktualisierungszyklus komplett ist, werden die Daten in die Live-Map und die App geladen. Normalerweise wird die Aktualisierung auf der [http://status.waze.com/ Status Seite] veröffentlicht, mit dem Satz: "Enthält Edits bis..." Die Straßen werden in der Anwendung zwischengespeichert und nur aktualisiert, wenn eine der drei folgenden Bedingungen erfüllt ist: * Man sucht eine bestimmte Position auf der Karte aus dem Adressbuch. * Man navigiert durch die Straße. * Die Straße ist älter als eine Woche. Man kann auch die Aktualisierung über das Optionen Menü in der Waze Anwendung erledigen, bevor man losfährt. Die Aktualisierung ist auch abhängig davon ob die Karte seitens Waze aktualisiert wurde oder nicht. Das Datum der Live Map ist dabei massgebend. ===Warum sehe ich Meldungen, die hunderte Kilometer entfernt liegen auf der App=== Waze zeigt Dir mit einem Pop-Up nur die Verkehrsmeldungen innerhalb des definierten Radius um Deinen Standort an. Dies ist abhängig von den Einstellungen der Waze-App resp. des Radius den Du definiert hast. Der Radius schliesst deine Route mit ein, wenn Du mit Navigation unterwegs bist. Die Minimaldistanz zu Deinem Standort auf der Straße beträgt 5 Kilometer. ===Wie schalte ich die Pop-Up Meldungen bei Stillstand aus?=== Es gibt keine Einstellung, mit der man nur die Pop-Ups selbst deaktivieren kann. Man kann die Pop-Up Meldungen dennoch ausschalten, gehe dazu ins: Menü -> Optionen -> Erweitert -> Datentransfer -> Verkehrsinformationen herunterladen ACHTUNG: Dadurch werden alle Meldungen ausgeschaltet inkl. Geschwindigkeiten bei Staus. ===Warum bewegen sich die Wazer auf der Karte nicht in Echtzeit?=== Andere Wazer sind auf der Karte der Waze-App sichtbar. Es besteht eine Verzögerung von 2-5 Minuten. Das hat mehrere Gründe: Sicherheitsgründe, Privatsphäre, Server-Kapazität und Netzwerk-Datenverkehr. Es wäre eine große Datenmenge erforderlich, um die Standorte aller Wazer im 2-Sekundentakt zu aktualisieren. ===Kann ich eine Verkehrsmeldung oder einen Unfall von zu Hause aus melden?=== Nein. Du kannst keine Meldungen irgendwo auf der Karte platzieren! Waze erlaubt nur Meldungen wie Polizei, Unfall, Gefahr, Blitzer etc. basierend auf Deiner ''aktuellen GPS-Position''. ===Kann ich anhand von Latitude und Longitude oder GPS Koordinaten navigieren?=== Ja. Im Suchfeld der Navigation ''Longitude, Latitude'' in Dezimalform eingeben Beispiel: United States, Disney's Epcot Center in Orlando, Florida findet man unter folgenden Koordinaten: "28.37529,-81.54942" Die Live-Map akzeptiert die selben Koordinaten auch im Suchfeld. ===Warum lernt Waze meine Routen nicht?=== Die Einstellung in der Waze-App "Lerne Fahrten zu häufigen Zielen" kann irreführend sein. Waze lernt nur Deine häufigen Ziele und wenn diese Einstellung im Menü aktiviert ist, erscheint ein Pop-Up, das dich nach Deinem Fahrziel fragt. Waze wählt die Route anhand der Einstellungen in der App (schnellste/kürzeste Route), der Geschwindigkeiten und den vorhandenen Echtzeit-Verkehrsdaten entsprechend der aktuellen Tageszeit aus. Wenn Waze nicht die von Dir erwartete Route anbietet, kann dies auch an falschen Geschwindigkeiten in den Segmenten liegen. Waze braucht exakte Geschwindigkeiten aller Segmente im Umfeld Deiner Route, damit die Berechnung richtig funktioniert. ===Erhalte ich Punkte bei fehlender oder schlechter Datenverbindung?=== Damit Waze korrekt funktioniert muss eine ständige Datenverbindung bestehen. Bei Unterbrechung der Mobilfunkverbindung wird Waze versuchen Daten für Verkehrs-Meldungen und Gefahren vom Server zu erhalten, wird aber nicht in der Lage sein, zuverlässige Informationen zu liefern. Im Bezug auf die Punkte sammelt Waze Daten während der Zeit, in der eine Verbindung besteht (auch bei kleineren Unterbrechungen). Damit diese Daten (Punkte, Fahrten etc.) den Server erreichen, muss die App während oder am Ende der Fahrt die Daten zum Server hochladen können. Waze sendet die Daten an den Server, wenn die App heruntergefahren wird. Wenn während dem Herunterfahren der App keine Verbindung zum Server besteht, gehen alle Daten, die den Server noch nicht erreicht haben verloren. Punkte und Fahrten werden dann natürlich nicht gezählt. ===Wie ändere ich mein Land/Staat in der Waze-App?=== Normalerweise wird man dem Land oder Staat zugeordnet, in dem man sich mit Waze fortbewegt und die meisten Punkte innerhalb der letzten 1-3 Wochen gemacht hat. Bewegt man sich in vielen Ländern oder Staaten, kann man dies Waze mitteilen auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"] und der Heimatstaat oder das Heimatland wird von Waze fest zugeteilt. ===Ränge in der Waze-App=== Jeder Benutzer fängt als Baby-Wazer an. Die Tabelle zeigt an, wie du die Ränge emporsteigen kannst. [[Image:RankWazeSt.png | 450px |center|]] {| border="1" align="center" style="text-align:center;" |[[Image:Wazer baby@2x.png |40px]] '''Baby Wazer''' |Willkommen in der Waze Welt. Wazer! Du bist jetzt ein Baby Wazer. Aber nicht für lange Zeit... Fahre 160 Kilometer um ein erwachsener Wazer zu werden. |- |[[Image:Happy@2x.png|40px]] '''Erwachsener Wazer''' |Du bist nun ein erwachsener Wazer und kannst dir deine Laune selbst aussuchen. Um ein Waze Krieger zu werden musst Du mehr Punkte machen... |- |[[Image:WazeWarrior.png|40px]] '''Waze Krieger''' |Beachte das Schild! Du hast die Top 10% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Dies beizubehalten wird nicht einfach sein... |- |[[Image:WazeKnight.png|40px]] '''Waze Ritter''' |Das Schwert gehört nun Dir! Du hast die Top 4% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Du bist fast ein Waze König... Halte Ausschau nach Möglichkeiten Punkte zu machen. |- |[[Image:KingWaze.png|40px]] '''Waze König''' |Du hast es geschafft! Du hast die Top 1% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Fahre in deiner Region herum wohl wissend, dass Du jetzt ein VIP bist... |} Um den königlichen Rang zu erreichen, musst du in den Top % von allen Wazern in deinem Land sein. In den USA wir dies nach Staaten berechnet. Die Top % werden einmal monatlich berechnet. Je mehr Wazer Punkte machen desto höher kann auch der Wert sein, den du erreichen musst um Schild, Schwert oder Krone zu erhalten. Dies kann zwar frustrierend sein, hilft aber zu garantieren, dass niemand die 'königliche' Ebene für immer hat - es gibt immer eine Chance für neue Wazer dies auch zu erreichen. =Dashboard und Echtzeit-Karte (Live-Map)= === Was ist das Dashboard? === Das [[Mein Dashboard|Dashboard]] ist die Seite, auf der alle persönlichen Konto Information und Statistiken zu finden sind wie: Punkte, gefahrene Strecken, usw.<br> Man kann sich anmelden unter:<br> https://www.waze.com/de/dashboard === Wann sind meine Straßen in der Live-Map zu sehen? === Dies sollte etwa aller 2-3 Tage geschehen. Wenn der visuelle Teil der Live Map nicht aktualisiert worden ist, sind die Änderungen dennoch vorhanden, sie sind zu sehen wenn man in die Karte klickt. Klickt man eine Straße an werden die kürzlich aktualisierten Daten angezeigt. Aktualisierungen der Karte in der Waze-App erscheinen zur gleichen Zeit. Das Datum des letzten Updates befindet sich links unterhalb der Live Map. dieses Datum ist auch für die Anwendung relevant. Neu aufgezeichnete Straßen sind erst in der Live Map zu sehen, wenn sie durch einen Editor bearbeitet wurden! =Punkte und Bonuspunkte= ===In welchem Zeitraum werden die wöchentlichen Punkte berechnet?=== Punkte werden von Montag bis Sonntag gezählt. Meldungen über die Top Drei werden normalerweise am Montag Morgen erscheinen. ===Wie werden die Punkte berechnet?=== Punkte werden nach der Anzahl der aktualisierten Segmente/Kreuzungen/anderer Objekte vergeben. Gefahrene Kilometer werden mit 3,2 Punkten (1 Meile = 5 Punkte) und 3 Beiträge im Forum mit 2 Punkten vergütet. Werden mehrere Segmente gleichzeitig geändert, wird nur 1 Punkt pro Segment vergeben. Du erhältst im gleichen Speichervorgang keine weiteren Punkte für das Ändern verschiedener Eigenschaften des gleichen Segments. Beispiel: Ändern der Segment-Ebene von 3 ausgewählten Segmenten (in einem Vorgang), gibt Dir 3 Punkte für die Änderung an 3 Segmenten. Straßennamen vergeben für unbenannte Segmente im selbigen Vorgang, kann in gewissen Fällen mehr Punkte geben. Eine Abbiegung verbieten oder zulassen zählt als eine Änderung der Abbiegung an der Kreuzung. Alle Änderungen an einer Kreuzung zählen nur ein einziges Mal. Es gibt keine weiteren Punkte für das mehrmalige Ändern der selben Abbiegung einer Kreuzung. Wird das gleiche Objekt mehrmals bearbeitet innerhalb von 24 Stunden, wird nur einmal ein Punkt pro Objekt in diesem Zeitraum gewährt. Werden größere Mengen an Änderungen gespeichert, erhältst Du nicht mehr als 150 Punkte pro Speichervorgang. Wenn Du mehr als 150 Änderungen auf dem Zähler des Karteneditors siehst, werden trotzdem nur maximal 150 Punkte pro Speichervorgang vergeben. Mehr Informationen zum Hintergrund der Berechnung gibt es: [http://www.waze.com/forum/viewtopic.php?f=14&t=10760&start=190 hier], oder auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. Suchbegriff: missing points. {| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1" |- ! Aktivität !! Punkte !! Einheit |- | Straßenberichte¹ || 6 || pro Meldung |- | Bericht kommentieren || 3 || pro Kommentar |- | Benzinpreise melden¹ || 8 || pro Meldung |- | Karten bearbeiten² || 1.5 || pro Bearbeitungsschritt³ |- | Aktualisierungsanfragen || 3 || pro gelöste Anfrage |- | Straßen benennen⁴ || 1 || pro Name |- | Hausnummer einfügen || 1 || pro Hausnummer |- | Foren Posts || 2 || pro 3 Posts |- | Road Goodies || 3-10 || pro Goodie |} {| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1" |- ! Aktivität !! pro Kilometer !! pro Meile |- | Normal fahren⁵ || 3.2 || 5 |- | Straßen fressen || 10 || 16 |- | Neue Straße aufzeichnen || 40 || 64 |} ¹ [[Der Waze Chat|Map-Chats]] und deren Kommentare geben keine Punkte. Damit Waze nicht zum Punkte sammeln misbraucht wird, sind die Meldungen zeitlich begrenzt. Dies gilt auch für die Preis-Meldungen an Tankstellen. ² Mehrfachbearbeitung (mehrere Straßen auswählen und bearbeiten) registriert alle obigen Änderungen separat, aber Änderungen an der Geometrie eines Segments, werden alle nur als eine Änderung an einem Segment angesehen. Beispiel: Mehrere Geometriepunkte an einem Segment verändern gibt nur 1 Punkt pro Segment. Der Karteneditor zählt Massenänderungen als eine "ungespeicherte Änderung" pro Massenänderung. Die Zahl, die Du im Zähler des Karteneditors siehst, ist nicht das Total der Punkte, die Du erhältst. ³ Im Moment werden zusätzliche Bonuspunkte für Karteneditoren vergeben. 300 Punkte pro 3000 Kartenbearbeitungen. Alle Änderungen werden zusätzlich mit 3 Punkten pro Änderung belohnt. ⁴ Neue Straßennamen geben nur Punkte, wenn das Segment nicht schon zuvor benannt war. ⁵ Mit oder ohne Navigation. === Bonuspunkte und weitere Bonbons=== Es gibt noch andere Möglichkeiten Punkte zu erhalten. In der Tabelle unten sind diese aufgeführt. Wenn Du Bonuspunkte erhältst, erscheint in der Waze-App eine Meldung, dass Du ein Bonbon auf Deiner Strecke findest. Fahre darüber und die Punkte werden Deiner wöchentlichen Statistik hinzugefügt. Die Bonbons erscheinen in der Regel an Feiertagen, wie z.B. zu Weihnachten, Ostern etc. Auf der Karte findest Du, je nach Feiertag, verschiedene Bonbons (Road Goodies), die Du überfahren und dafür die Punkte einsammeln kannst. Manchmal kann es sein, dass ein Bonbon nicht auf direktem Weg zu erreichen ist. Keine Sorge, das Bonbon erscheint nochmals, auch wenn Du Waze ein anderes Mal startest. Wenn Du die Anzeige der Bonbons in der Waze-App deaktiviert hast, werden die Punkte automatisch hinzugefügt. {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" |- ! scope="col" width="200"| Aufgabe ! Punkte ! scope="col" width="200"| Bemerkungen |- | Deine ersten 16 Kilometer || 25 || |- | Deine erste Meldung || 25 || |- | Deine erste Meldung am Wochenende || 30 || |- | Erste Meldung eines Kartenfehlers || 50 || |- | Erster Freund || 200 || Dies kann nur erreicht werden, wenn Du Dich mit Facebook verbindest. Dein Freund muß auch mit Facebook verbunden sein. |- | Erste Woche¹ in der Du 2 Tage hintereinander gefahren bist || 100 || |- | Erste Woche¹ in der Du 3 Tage hintereinander gefahren bist || 200 || |- | Dein erster Edit auf der Karte || 200 || |- | Erste Woche¹ in der Du 4 Tage hintereinander gefahren bist || 300 || |- | Bearbeiten von 50 Kartenfehlern || 500 || |- | Wöchentlicher Top User in deinem Land || 500 || |- | 3000 Edits auf der Karte erledigt || 300 || Dies kann immer wieder erreicht werden. Bonbon kann auch erst erscheinen, wenn die Ränge auf dem Server aktualisiert wurden. |- | 800 Kilometer gefahren in einer Woche¹ || 1000 || |- | Fünf Freunde || 2000 || Siehe "Erster Freund" |- |} ¹ Die Punkte werden Montag bis Sonntag berechnet. Wenn Du der Meinung bist einen Bonus freigeschaltet zu haben, aber das Bonus-Bonbon auf der Straße nicht angetroffen hast, warte eine weitere Woche. Wenn es sich um einen Bonus handelt, der mehrere Tage benötigt um freigeschaltet zu werden, warte den Montag ab, denn der Kalender wird anfangs Woche am Montag zurückgesetzt. Das Bonus-Bonbon erscheint nicht, wenn Dein Bonus nicht zwischen Montag und Montag freigeschaltet wurde. Auch können einige Bonbons nicht in der gleichen Woche freigeschaltet werden, Du musst also eine weitere Woche abwarten. =Sonstiges= ===Wie kann ich mein Benutzerkonto löschen?=== Benutzerkonten können nicht gelöscht werden vom Benutzer, sende eine Anfrage auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"] mit Benutzernamen und registrierter E-Mail Adresse. ===Wie kann ich meinen Benutzernamen ändern?=== Im Moment ist dies nicht möglich. ===Wie eröffne ich ein Support Ticket/Anfrage an Waze?=== Das Forum ist ein primärer Kanal, um von der Community Hilfe zu erhalten. Einige Mitarbeiter von Waze beantworten auch manchmal Fragen, mehrheitlich zu Fehlern in der App oder WME. Wenn Du direkte Hilfe vom Support brauchst, gibt es ein Formular dafür: #Gehe zur [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. #In der Quick Help Box, kannst Du Dein Problem eingeben im ersten Feld. #Ist Dein Problem nicht bekannt in der automatischen Hilfe, ''klick'' hier: '''"Still can't find what you're looking for? click here"''' Ein weiterer Dialog öffnet sich und Du kannst weitere Informationen finden. #Ist Dein Problem auch hier nicht beschrieben ''klick'' hier: '''"If you cannot find your answer, Please click here."''' #Füll das Formular aus mit allen Informationen, die benötigt werden, Permalinks aus dem Waze Map-Editor, Links zu App-Screenshots etc. in der More Details Box. #''Klick'' auf '''Submit''' Es wir keine Bestätigung an Dich gesendet, dass Dein Ticket eröffnet wurde, aber Du erhältst in der Regel in ein paar Tagen eine Antwort. [[Image:NanoRep-Box.png|center]] ===Wie lauten die Adressen der RSS Feeds für Waze?=== Hier findest du die [[RSS Feeds|Anleitung]] und eine Feed List. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 10aff8d4917711e667c32133c268fc730308e214 12003 12002 2017-10-29T20:36:23Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Diese Seite über die häufig gestellten Fragen in Waze sollte mit dem [http://www.waze.com/faq/ Official FAQ] und dem [http://www.waze.com/faq/technical_faq/ Technical FAQ] gelesen werden. Der [[Glossar|Glossar]] erklärt die Begriffe und die speziellen Bezeichnungen in Waze. =WME - Karteneditor= === Welche Browser werden vom Waze Map-Editor unterstützt? === Waze empfiehlt [http://www.google.com/chrome Google Chrome] Browser oder das [http://www.google.com/chromeframe Google Chrome Frame] Plugin mit dem Internet Explorer zu verwenden. Die Unterstützung für Microsoft Internet Explorer (IE) ist limitiert und manche Funktionen arbeiten evtl. nicht korrekt. Folgende Browser funktionieren mit dem Waze Map-Editor: *[http://www.google.com/chrome Chrome] (Empfohlen) *[http://www.apple.com/safari Safari] *[http://www.mozilla-europe.org/nl/firefox Firefox] === Was ist die Base-Map? === Die Base-Map ist eine Basis-Karte, die von Waze implementiert wurde. Die Base-Map ist in ihrer Rohform komplett unbearbeitet, das heisst: Es sind nur Straßen vorhanden und keine Straßen- oder Ortsnamen. Die Karte ist schlecht navigierbar und in der Regel müssen alle Straßen auch in ihrer Klassifizierung überprüft werden. Einbahnstraßen sind inexistent und auch alle Abbiegungen müssen erst noch gesetzt werden, bevor eine saubere Navigation möglich ist. Die Base-Map Straßen haben auch alle keine Fahrtrichtung. Deutschland ist beispielsweise ein Base-Map Land. === Wieso sind die Satellitenbilder inexistent oder in schlechter Auflösung? === Aufgrund des Geschäftsmodells, welches die Anwendung kostenlos für die Benutzer hält, ist man limitiert in den Quellen. Waze bezieht die Luftbilder von Bing. Waze verwendet keine anderen kommerziellen Quellen. Wenn man alte oder schlechte Bilder vorfindet kann man dies mit diesem [https://docs.google.com/a/waze.com/spreadsheet/viewform?hl=en_US&formkey=dDFhcGpGNGdWWmRiTXMxa2tOS2RlYWc6MQ#gid=0 Formular] melden. === Was ist der Waze Map-Editor? === Der Waze Map-Editor oder "WME" (interner Code Name Papyrus) ist der Name des Karteneditors.<br> Man kann sich anmelden unter:<br> https://www.waze.com/de/editor/ === Was sind Fahrten (Drives)? === "Drives" sind die Fahrten, die Du mit eingeschaltener Waze-App gemacht hast. Während der Fahrt speichert Waze die gefahrene Strecke (Ort, Zeit und Geschwindigkeiten) und überträgt diese Infos an den Server. Diese Daten validieren den bestehenden Zustand der Karte, lernen durchschnittliche Fahrzeiten ein (sogen. Segmentgeschwindigkeitsdaten) und lernen den Wazeservern gebräuchliche Wege. Die Benutzer oder Area-Manager, welche die Karte bearbeiten, können im Karteneditor die gefahrenen Strecken anhand anonymisierter GPS-Punkte sehen und die Straßen auf der Karte wenn nötig einzeichnen oder im Verlauf anpassen. Jeder Benutzer kann seine eigenen Fahrten unter "Fahrten" im Karteneditor anschauen. === Wann sehe ich meine Fahrten im Karteneditor? === Die Fahrten sind nach etwa einer Stunde im Waze Map-Editor sichtbar. Kurze Fahrten unter 50 Kilometer sind meist in weniger als 15 Minuten im Waze Map-Editor. Wenn die Server Probleme haben oder die Fahrten länger als 150 Kilometer sind, kann es sein, dass es bis zu einer Woche dauert. Sind die Fahrten nach einer Woche nicht vorhanden, sollte man dies via [https://world.waze.com/support/ Quick Help] auf der Support-Seite melden. Benutze den Mail-Link und beschreibe Dein Problem. Ein Blick auf die [http://status.waze.com/ Status Seite] oder ins [http://world.waze.com/forum Forum] kann auch hilfreich sein. === Was ist eine gesperrte Straße im Waze Map-Editor? (Lock)=== Die "Sperren" Funktion bewirkt folgendes: Ein gesperrtes Segment kann nicht durch Editoren mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]] bearbeitet werden. Der Rang eines Editors ermöglicht Ihm ein Segment mit einer "Bearbeitungssperre" (Lock) auf maximal seinem Editorenlevel zu versehen. Sinnvoll ist dies als Schutz bei wichtigen Hauptverkehrsadern wie Autobahnen (Freeway - Locklevel 5) oder Bundesstraßen (Locklevel 3). Gesperrte Segmente beeinflussen die Abbiegungen der Kreuzungen an den Enden der Segmente. Wenn eine Abiegung nicht geändert werden kann, ist möglicherweise ein Segment an der Kreuzung gesperrt. Zum entsperren der Segmente, richtet man eine Anfrage an das betreffende Forum. Es gibt Threads zum Thema Entsperren von Straßen.. Ausserdem kann oft ein L5/L6-Editor im Chat weiter helfen. Lies zum Thema "Sperren von Straßen" diese [[Sperren von Straßen (Locking)|Seite]]. ===Was ist das Penalty-System=== Für die Erstellung einer Route verwendet Waze unter anderem ein System von Penalties (Zeitzuschlägen). Das Penalty-System ist dafür verantwortlich, den schnellsten Weg zu finden. Es eliminiert mögliche Routen indem es für die Berechnung mehr Zeit (pro Segment oder Kreuzung) vergibt als erwartet.<br> Infos in deutscher Sprache findest Du auf dieser Seite: [[Wie Waze Routen kalkuliert]]<br> Infos in Englisch findest Du auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. Gib in unter "Stell eine Frage" der nanoRep Box das Wort "Penalties" ein.<br> ===Unterstützt Waze zeitlich begrenze Abbiegeverbote?=== Ja, Informationen dazu findest Du hier: [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] =Waze-App= === Was bedeuten die kleinen Punkte auf den Straßen? === Dies sind Straßen, die noch nicht bestätigt wurden. Das heisst, dass diese Straßen noch nie befahren wurden, seit sie mit dem Karteneditor erstellt oder mit der Basis-Karte importiert wurden. Es kann sein, dass die Kreuzungen und die Geometrie nicht zu 100% korrekt sind, daher sollte man diesen Straßen Beachtung schenken. Wenn über solche Straßen gefahren wird, ändert sich das Waze-Icon auf dem Bildschirm und zeigt einen Pacman an der die Punkte verspeist. Dies gibt Punkte und bestätigt die Straße für Waze. Diese Straßen werden auch oft [[Glossar#Pacman_Roads.2C_Pacman_Stra.C3.9Fen|Pacman-Straßen]] genannt. Mehr dazu [[Ablauf_der_Aktualisierungsprozesse#Punkte_fressen.28Munching.2FPacman-Roads.29|hier]]. Die Punkte erhält nur, wer die Straße als erstes mit dem Pacman befährt. Die Straßen können noch länger unbestätigt erscheinen. === Was ist, wenn man beim Fahren keine Straße in der App sieht? === Wenn eine Straße befahren wird, die nicht in der App sichtbar ist, speichert Waze zwar die Routeninformationen wie gewohnt, fügt aber die Straße nicht ohne weiteres zum Karteneditor oder der Live Map hinzu. In diesem Fall kann man die Straße über die App [[Zeichne Straße auf |aufzeichnen]]. Die aufgezeichnete Straße erscheint rot in Waze und setzt auch an verschiedenen Stellen Kreuzungen, wo Waze z.B. eine Abbiegung während der Fahrt entdeckt. Wenn Waze wieder zurück auf eine vorhandene Straße kommt, sollte die Aufnahme automatisch pausieren. Man sollte diese Funktion nur verwenden, wenn auf Straßen gefahren wird, die noch nicht auf der Karte existieren! Waze zeichnet bei ungenauem GPS-Signal Straßen auf, wo schon welche vorhanden sind, da die Anwendung in diesem Fall der Meinung ist, dass man sich nicht auf einer existierenden Straße befindet. Dies führt zu unerwünschten Korrekturen durch die Editoren oder Area-Manager. Es ist auch zu beachten, dass Waze bei fehlender oder schlechter Netz-Abdeckung die Karte nicht in die Anwendung herunterladen kann. Das heisst: es ist keine Karte sichtbar, aber sie ist trotzdem bereits vorhanden. Auch in diesem Moment können Straßen aufgezeichnet werden. Daher Vorsicht bei der Aufzeichnung! === Ich habe neue Straßen aufgezeichnet - was nun? === Die neu aufgezeichneten Straßen erscheinen innerhalb kurzer Zeit im Karteneditor, wo Du diese weiter bearbeiten kannst. Bitte erledige dies innerhalb kurzer Frist, sonst wird die Karte nicht erweitert und die Benutzer können nicht von deiner Arbeit profitieren. Melde Dich dazu im Karteneditor an und bearbeite die Straßen. Details wie Straßenname, Stadt-/Gemeindename, Fahrtrichtungen, Straßentyp usw. sollten alle im Karteneditor ergänzt werden. Dabei sollte man die neue Straße mit bereits bestehenden verbinden und die Abbiegeverbote korrekt setzen. Ansonsten kann die Straße nicht oder nicht richtig bei der Navigation berücksichtigt werden. === Wann sehe ich meine Straßen in der Waze-App? === Das normale Verfahren ist, dass in regelmäßigen Abständen ein Aktualisierungsprozess auf den Servern ausgeführt wird (Stand 2016: 1-3x pro Woche). Wenn er beginnt, werden alle Edits bis zu diesem Zeitpunkt in den aktuellen Karten-Aktualisierungszyklus aufgenommen. Nachdem Aktualisierungszyklus komplett ist, werden die Daten in die Live-Map und die App geladen. Normalerweise wird die Aktualisierung auf der [http://status.waze.com/ Status Seite] veröffentlicht, mit dem Satz: "Enthält Edits bis..." Die Straßen werden in der Anwendung zwischengespeichert und nur aktualisiert, wenn eine der drei folgenden Bedingungen erfüllt ist: * Man sucht eine bestimmte Position auf der Karte aus dem Adressbuch. * Man navigiert durch die Straße. * Die Straße ist älter als eine Woche. Man kann auch die Aktualisierung über das Optionen Menü in der Waze Anwendung erledigen, bevor man losfährt. Die Aktualisierung ist auch abhängig davon ob die Karte seitens Waze aktualisiert wurde oder nicht. Das Datum der Live Map ist dabei massgebend. ===Warum sehe ich Meldungen, die hunderte Kilometer entfernt liegen auf der App=== Waze zeigt Dir mit einem Pop-Up nur die Verkehrsmeldungen innerhalb des definierten Radius um Deinen Standort an. Dies ist abhängig von den Einstellungen der Waze-App resp. des Radius den Du definiert hast. Der Radius schliesst deine Route mit ein, wenn Du mit Navigation unterwegs bist. Die Minimaldistanz zu Deinem Standort auf der Straße beträgt 5 Kilometer. ===Warum bewegen sich die Wazer auf der Karte nicht in Echtzeit?=== Andere Wazer sind auf der Karte der Waze-App sichtbar. Es besteht eine Verzögerung von 2-5 Minuten. Das hat mehrere Gründe: Sicherheitsgründe, Privatsphäre, Server-Kapazität und Netzwerk-Datenverkehr. Es wäre eine große Datenmenge erforderlich, um die Standorte aller Wazer im 2-Sekundentakt zu aktualisieren. ===Kann ich eine Verkehrsmeldung oder einen Unfall von zu Hause aus melden?=== Nein. Du kannst keine Meldungen irgendwo auf der Karte platzieren! Waze erlaubt nur Meldungen wie Polizei, Unfall, Gefahr, Blitzer etc. basierend auf Deiner ''aktuellen GPS-Position''. ===Kann ich anhand von Latitude und Longitude oder GPS Koordinaten navigieren?=== Ja. Im Suchfeld der Navigation ''Longitude, Latitude'' in Dezimalform eingeben Beispiel: United States, Disney's Epcot Center in Orlando, Florida findet man unter folgenden Koordinaten: "28.37529,-81.54942" Die Live-Map akzeptiert die selben Koordinaten auch im Suchfeld. ===Warum lernt Waze meine Routen nicht?=== Die Einstellung in der Waze-App "Lerne Fahrten zu häufigen Zielen" kann irreführend sein. Waze lernt nur Deine häufigen Ziele und wenn diese Einstellung im Menü aktiviert ist, erscheint ein Pop-Up, das dich nach Deinem Fahrziel fragt. Waze wählt die Route anhand der Einstellungen in der App (schnellste/kürzeste Route), der Geschwindigkeiten und den vorhandenen Echtzeit-Verkehrsdaten entsprechend der aktuellen Tageszeit aus. Wenn Waze nicht die von Dir erwartete Route anbietet, kann dies auch an falschen Geschwindigkeiten in den Segmenten liegen. Waze braucht exakte Geschwindigkeiten aller Segmente im Umfeld Deiner Route, damit die Berechnung richtig funktioniert. ===Erhalte ich Punkte bei fehlender oder schlechter Datenverbindung?=== Damit Waze korrekt funktioniert muss eine ständige Datenverbindung bestehen. Bei Unterbrechung der Mobilfunkverbindung wird Waze versuchen Daten für Verkehrs-Meldungen und Gefahren vom Server zu erhalten, wird aber nicht in der Lage sein, zuverlässige Informationen zu liefern. Im Bezug auf die Punkte sammelt Waze Daten während der Zeit, in der eine Verbindung besteht (auch bei kleineren Unterbrechungen). Damit diese Daten (Punkte, Fahrten etc.) den Server erreichen, muss die App während oder am Ende der Fahrt die Daten zum Server hochladen können. Waze sendet die Daten an den Server, wenn die App heruntergefahren wird. Wenn während dem Herunterfahren der App keine Verbindung zum Server besteht, gehen alle Daten, die den Server noch nicht erreicht haben verloren. Punkte und Fahrten werden dann natürlich nicht gezählt. ===Wie ändere ich mein Land/Staat in der Waze-App?=== Normalerweise wird man dem Land oder Staat zugeordnet, in dem man sich mit Waze fortbewegt und die meisten Punkte innerhalb der letzten 1-3 Wochen gemacht hat. Bewegt man sich in vielen Ländern oder Staaten, kann man dies Waze mitteilen auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"] und der Heimatstaat oder das Heimatland wird von Waze fest zugeteilt. ===Ränge in der Waze-App=== Jeder Benutzer fängt als Baby-Wazer an. Die Tabelle zeigt an, wie du die Ränge emporsteigen kannst. [[Image:RankWazeSt.png | 450px |center|]] {| border="1" align="center" style="text-align:center;" |[[Image:Wazer baby@2x.png |40px]] '''Baby Wazer''' |Willkommen in der Waze Welt. Wazer! Du bist jetzt ein Baby Wazer. Aber nicht für lange Zeit... Fahre 160 Kilometer um ein erwachsener Wazer zu werden. |- |[[Image:Happy@2x.png|40px]] '''Erwachsener Wazer''' |Du bist nun ein erwachsener Wazer und kannst dir deine Laune selbst aussuchen. Um ein Waze Krieger zu werden musst Du mehr Punkte machen... |- |[[Image:WazeWarrior.png|40px]] '''Waze Krieger''' |Beachte das Schild! Du hast die Top 10% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Dies beizubehalten wird nicht einfach sein... |- |[[Image:WazeKnight.png|40px]] '''Waze Ritter''' |Das Schwert gehört nun Dir! Du hast die Top 4% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Du bist fast ein Waze König... Halte Ausschau nach Möglichkeiten Punkte zu machen. |- |[[Image:KingWaze.png|40px]] '''Waze König''' |Du hast es geschafft! Du hast die Top 1% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Fahre in deiner Region herum wohl wissend, dass Du jetzt ein VIP bist... |} Um den königlichen Rang zu erreichen, musst du in den Top % von allen Wazern in deinem Land sein. In den USA wir dies nach Staaten berechnet. Die Top % werden einmal monatlich berechnet. Je mehr Wazer Punkte machen desto höher kann auch der Wert sein, den du erreichen musst um Schild, Schwert oder Krone zu erhalten. Dies kann zwar frustrierend sein, hilft aber zu garantieren, dass niemand die 'königliche' Ebene für immer hat - es gibt immer eine Chance für neue Wazer dies auch zu erreichen. =Dashboard und Echtzeit-Karte (Live-Map)= === Was ist das Dashboard? === Das [[Mein Dashboard|Dashboard]] ist die Seite, auf der alle persönlichen Konto Information und Statistiken zu finden sind wie: Punkte, gefahrene Strecken, usw.<br> Man kann sich anmelden unter:<br> https://www.waze.com/de/dashboard === Wann sind meine Straßen in der Live-Map zu sehen? === Dies sollte etwa aller 2-3 Tage geschehen. Wenn der visuelle Teil der Live Map nicht aktualisiert worden ist, sind die Änderungen dennoch vorhanden, sie sind zu sehen wenn man in die Karte klickt. Klickt man eine Straße an werden die kürzlich aktualisierten Daten angezeigt. Aktualisierungen der Karte in der Waze-App erscheinen zur gleichen Zeit. Das Datum des letzten Updates befindet sich links unterhalb der Live Map. dieses Datum ist auch für die Anwendung relevant. Neu aufgezeichnete Straßen sind erst in der Live Map zu sehen, wenn sie durch einen Editor bearbeitet wurden! =Punkte und Bonuspunkte= ===In welchem Zeitraum werden die wöchentlichen Punkte berechnet?=== Punkte werden von Montag bis Sonntag gezählt. Meldungen über die Top Drei werden normalerweise am Montag Morgen erscheinen. ===Wie werden die Punkte berechnet?=== Punkte werden nach der Anzahl der aktualisierten Segmente/Kreuzungen/anderer Objekte vergeben. Gefahrene Kilometer werden mit 3,2 Punkten (1 Meile = 5 Punkte) und 3 Beiträge im Forum mit 2 Punkten vergütet. Werden mehrere Segmente gleichzeitig geändert, wird nur 1 Punkt pro Segment vergeben. Du erhältst im gleichen Speichervorgang keine weiteren Punkte für das Ändern verschiedener Eigenschaften des gleichen Segments. Beispiel: Ändern der Segment-Ebene von 3 ausgewählten Segmenten (in einem Vorgang), gibt Dir 3 Punkte für die Änderung an 3 Segmenten. Straßennamen vergeben für unbenannte Segmente im selbigen Vorgang, kann in gewissen Fällen mehr Punkte geben. Eine Abbiegung verbieten oder zulassen zählt als eine Änderung der Abbiegung an der Kreuzung. Alle Änderungen an einer Kreuzung zählen nur ein einziges Mal. Es gibt keine weiteren Punkte für das mehrmalige Ändern der selben Abbiegung einer Kreuzung. Wird das gleiche Objekt mehrmals bearbeitet innerhalb von 24 Stunden, wird nur einmal ein Punkt pro Objekt in diesem Zeitraum gewährt. Werden größere Mengen an Änderungen gespeichert, erhältst Du nicht mehr als 150 Punkte pro Speichervorgang. Wenn Du mehr als 150 Änderungen auf dem Zähler des Karteneditors siehst, werden trotzdem nur maximal 150 Punkte pro Speichervorgang vergeben. Mehr Informationen zum Hintergrund der Berechnung gibt es: [http://www.waze.com/forum/viewtopic.php?f=14&t=10760&start=190 hier], oder auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. Suchbegriff: missing points. {| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1" |- ! Aktivität !! Punkte !! Einheit |- | Straßenberichte¹ || 6 || pro Meldung |- | Bericht kommentieren || 3 || pro Kommentar |- | Benzinpreise melden¹ || 8 || pro Meldung |- | Karten bearbeiten² || 1.5 || pro Bearbeitungsschritt³ |- | Aktualisierungsanfragen || 3 || pro gelöste Anfrage |- | Straßen benennen⁴ || 1 || pro Name |- | Hausnummer einfügen || 1 || pro Hausnummer |- | Foren Posts || 2 || pro 3 Posts |- | Road Goodies || 3-10 || pro Goodie |} {| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1" |- ! Aktivität !! pro Kilometer !! pro Meile |- | Normal fahren⁵ || 3.2 || 5 |- | Straßen fressen || 10 || 16 |- | Neue Straße aufzeichnen || 40 || 64 |} ¹ [[Der Waze Chat|Map-Chats]] und deren Kommentare geben keine Punkte. Damit Waze nicht zum Punkte sammeln misbraucht wird, sind die Meldungen zeitlich begrenzt. Dies gilt auch für die Preis-Meldungen an Tankstellen. ² Mehrfachbearbeitung (mehrere Straßen auswählen und bearbeiten) registriert alle obigen Änderungen separat, aber Änderungen an der Geometrie eines Segments, werden alle nur als eine Änderung an einem Segment angesehen. Beispiel: Mehrere Geometriepunkte an einem Segment verändern gibt nur 1 Punkt pro Segment. Der Karteneditor zählt Massenänderungen als eine "ungespeicherte Änderung" pro Massenänderung. Die Zahl, die Du im Zähler des Karteneditors siehst, ist nicht das Total der Punkte, die Du erhältst. ³ Im Moment werden zusätzliche Bonuspunkte für Karteneditoren vergeben. 300 Punkte pro 3000 Kartenbearbeitungen. Alle Änderungen werden zusätzlich mit 3 Punkten pro Änderung belohnt. ⁴ Neue Straßennamen geben nur Punkte, wenn das Segment nicht schon zuvor benannt war. ⁵ Mit oder ohne Navigation. === Bonuspunkte und weitere Bonbons=== Es gibt noch andere Möglichkeiten Punkte zu erhalten. In der Tabelle unten sind diese aufgeführt. Wenn Du Bonuspunkte erhältst, erscheint in der Waze-App eine Meldung, dass Du ein Bonbon auf Deiner Strecke findest. Fahre darüber und die Punkte werden Deiner wöchentlichen Statistik hinzugefügt. Die Bonbons erscheinen in der Regel an Feiertagen, wie z.B. zu Weihnachten, Ostern etc. Auf der Karte findest Du, je nach Feiertag, verschiedene Bonbons (Road Goodies), die Du überfahren und dafür die Punkte einsammeln kannst. Manchmal kann es sein, dass ein Bonbon nicht auf direktem Weg zu erreichen ist. Keine Sorge, das Bonbon erscheint nochmals, auch wenn Du Waze ein anderes Mal startest. Wenn Du die Anzeige der Bonbons in der Waze-App deaktiviert hast, werden die Punkte automatisch hinzugefügt. {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" |- ! scope="col" width="200"| Aufgabe ! Punkte ! scope="col" width="200"| Bemerkungen |- | Deine ersten 16 Kilometer || 25 || |- | Deine erste Meldung || 25 || |- | Deine erste Meldung am Wochenende || 30 || |- | Erste Meldung eines Kartenfehlers || 50 || |- | Erster Freund || 200 || Dies kann nur erreicht werden, wenn Du Dich mit Facebook verbindest. Dein Freund muß auch mit Facebook verbunden sein. |- | Erste Woche¹ in der Du 2 Tage hintereinander gefahren bist || 100 || |- | Erste Woche¹ in der Du 3 Tage hintereinander gefahren bist || 200 || |- | Dein erster Edit auf der Karte || 200 || |- | Erste Woche¹ in der Du 4 Tage hintereinander gefahren bist || 300 || |- | Bearbeiten von 50 Kartenfehlern || 500 || |- | Wöchentlicher Top User in deinem Land || 500 || |- | 3000 Edits auf der Karte erledigt || 300 || Dies kann immer wieder erreicht werden. Bonbon kann auch erst erscheinen, wenn die Ränge auf dem Server aktualisiert wurden. |- | 800 Kilometer gefahren in einer Woche¹ || 1000 || |- | Fünf Freunde || 2000 || Siehe "Erster Freund" |- |} ¹ Die Punkte werden Montag bis Sonntag berechnet. Wenn Du der Meinung bist einen Bonus freigeschaltet zu haben, aber das Bonus-Bonbon auf der Straße nicht angetroffen hast, warte eine weitere Woche. Wenn es sich um einen Bonus handelt, der mehrere Tage benötigt um freigeschaltet zu werden, warte den Montag ab, denn der Kalender wird anfangs Woche am Montag zurückgesetzt. Das Bonus-Bonbon erscheint nicht, wenn Dein Bonus nicht zwischen Montag und Montag freigeschaltet wurde. Auch können einige Bonbons nicht in der gleichen Woche freigeschaltet werden, Du musst also eine weitere Woche abwarten. =Sonstiges= ===Wie kann ich mein Benutzerkonto löschen?=== Benutzerkonten können nicht gelöscht werden vom Benutzer, sende eine Anfrage auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"] mit Benutzernamen und registrierter E-Mail Adresse. ===Wie kann ich meinen Benutzernamen ändern?=== Ja. In der App unter "Account und Anmeldung" ===Wie eröffne ich ein Support Ticket/Anfrage an Waze?=== Das Forum ist ein primärer Kanal, um von der Community Hilfe zu erhalten. Einige Mitarbeiter von Waze beantworten auch manchmal Fragen, mehrheitlich zu Fehlern in der App oder WME. Wenn Du direkte Hilfe vom Support brauchst, gibt es ein Formular dafür: #Gehe zur [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. #In der Quick Help Box, kannst Du Dein Problem eingeben im ersten Feld. #Ist Dein Problem nicht bekannt in der automatischen Hilfe, ''klick'' hier: '''"Still can't find what you're looking for? click here"''' Ein weiterer Dialog öffnet sich und Du kannst weitere Informationen finden. #Ist Dein Problem auch hier nicht beschrieben ''klick'' hier: '''"If you cannot find your answer, Please click here."''' #Füll das Formular aus mit allen Informationen, die benötigt werden, Permalinks aus dem Waze Map-Editor, Links zu App-Screenshots etc. in der More Details Box. #''Klick'' auf '''Submit''' Es wir keine Bestätigung an Dich gesendet, dass Dein Ticket eröffnet wurde, aber Du erhältst in der Regel in ein paar Tagen eine Antwort. [[Image:NanoRep-Box.png|center]] ===Wie lauten die Adressen der RSS Feeds für Waze?=== Hier findest du die [[RSS Feeds|Anleitung]] und eine Feed List. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 3971c74f931f98a06b722802dcb56ded72d142c8 0 81 12004 2017-10-29T20:42:32Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Einleitung== Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Einleitung== Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Man kann alle Objekte auf der Karte beliebig weiter bearbeiten oder löschen. Das gewünschte kann jeweils mit einem Klick ausgewählt und nach Belieben verändert werden. Was mit jedem Objekt oder Segment alles möglich ist, unterscheidet sich nach dem Typ des jeweiligen Objekts und den Rechten des Benutzers. Lies [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] bevor Du loslegst und alles andere findest Du hier in den [[Anleitung_zum_Bearbeiten_der_Karte|Anleitungen]]. ==Anmeldung im Karteneditor== * https://www.waze.com/de/editor/ Melde Dich mit Deinem Benutzernamen und Passwort an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Gebräuchliche Funktionen= ==Die Ebenen== Anzeigen oder verbergen über das Symbol [[Image:Layers-Auswahl.png]] in der oberen, rechten Ecke der Karte. * Mehr Informationen über die Ebenen findest Du hier: [[Der_Waze_Map-Editor#Ebenen-Auswahl|Beschreibung der Ebenen]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Luftaufnahmen== Kann über die Ebene ausgeschaltet werden. Ebenso können GPS-Punkte, Straßen, Orientierungspunkte etc. über die Ebenen gesteuert werden. Du kannst auch an den Straßen arbeiten, wenn die Ebene der Luftaufnahmen ausgeschaltet ist. So kannst Du Straßen anhand der GPS-Punkte ausrichten auf der Karte. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Eine Straße einzeichnen== # Fahre mit der Maus auf dieses Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Straße''' aus. # Klicke in der Karte auf die Stelle, wo du mit dem Einzeichnen beginnen willst. # Ziehe so die Straße an das gewünschte Ende. Jeder Klick dazwischen erstellt einen Geometriepunkt zum Bearbeiten. # Beende mit einem Doppelklick an der Stelle, wo Du mit dem Einzeichnen aufhören willst. * Bevor die Straße oder ein Kreisverkehr auf der Karte erscheint, musst Du speichern. * Für mehr Informationen, lies [[Erstellen und bearbeiten eines Segments]]. Während Du eine neue Straße einzeichnest, kannst Du den Kartenausschnitt mit der linken Maustaste verschieben, bevor Du mit dem Doppelklick das Einzeichnen beendest. Eine neu eingezeichnete Straße wird auf der Karte gleich dargestellt, wie beim Aufzeichnen über die App. Das heißt: Einbahn in Fahrtrichtung rot. Dies ändert sich erst, wenn Du die Straße benannt resp. ihre Eigenschaften bearbeitet hast. Solange Du an Kreuzungen oder Straßen arbeitest, färben sie sich unterschiedlich, bis Du die Änderungen gespeichert hast. So hast Du immer den Überblick, welche Arbeiten noch nicht gespeichert wurden und woran Du gerade gearbeitet hast. '''Eine wichtige Regel Lautet:'''<br> Ein [[Glossar#Segment_oder_Segmente|Segment]] kann niemals mit sich selbst verbunden werden! Eine Straße kann zwar rund gezeichnet werden, aber es entsteht keine Kreuzung, wenn sie sich selbst berührt. '''Bearbeitung ohne Anzeige der Straßen'''<br> Du kannst Straßen und Kreuzungen auch bearbeiten, wenn die Anzeige in der Straßen-Ebene ausgeschaltet ist. Wenn die Ebene der Luftaufnahmen eingeschaltet ist, siehst Du immer noch die Karte. Wenn Du mit der Maus über die verborgenen Straßen fährst, leuchten diese auf. Das Gleiche gilt für Kreuzungen. So kannst Du bequem Straßen an die Karte anpassen oder die GPS-Punkte, wenn der GPS-Layer angeschaltet ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen verbinden== Wenn eine Straße an eine andere geführt wird, verbindet sie sich automatisch durch eine Kreuzung. # Eine neue Straße verbindet sich automatisch mit bereits bestehenden Straßen, wenn man sie aneinanderführt. # Wenn bereits bestehende Straßen am ihrem Ende an eine andere Straße geführt werden, verbinden sie sich automatisch miteinander durch eine Kreuzung. # Wird eine Straße mit einer Kreuzung am Ende an eine andere Straße hingeführt verbindet sich die Kreuzung mit dem bestehenden Segment. An der Kreuzung ziehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen-Schlaufen== Wenn eine Straße eingezeichnet wird, die an beiden Enden das gleiche Segment berührt, wird nur die Kreuzung am Ende der neu eingezeichneten Straße erstellt. Um die Anfangs-Kreuzung zu erstellen: # Das Ende des Segments wegziehen. # Das Segment deselektieren (eine freie Stelle in der Karte anklicken). # Das Segment nochmals auswählen und an die gewünschte Stelle ziehen. Wenn ein Segment gezeichnet wird, das den Anfangs- und Endpunkt auf der selben [[Kreuzungen#Schlaufen|Kreuzung]] hat, funktioniert das obige nicht, und falls doch, sind die Abbiegungen an der Kreuzung falsch. Dieses Segment muss dann durch eine Kreuzung [[#Ein Segment teilen|unterbrochen]] und alle Segmente einzeln verbunden werden. Danach die Abbiegeverbote nicht vergessen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Abbiegungen== Abbiegungen werden über die Verbindungspfeile am Ende jedes verbundenen Segments gesteuert. [[Image:lotsa_turns.jpg|center|frame]] *Rot bedeutet abbiegen verboten, grün bedeutet abbiegen erlaubt in der Richtung, in die die Pfeile zeigen. Wenn ein Pfeil angeklickt wird, ändert dies die Abbiegung von Erlaubt auf Verboten und umgekehrt. Beim Neueinzeichnen einer Straße sind die Pfeile generell rot. *Der rote Pfeil hat an der Spitze ein kleines -, um Farbenblinden die Bearbeitung zu erleichtern. *Der gelbe Pfeil zeigt zeitlich beschränkte Abbiegeverbote an. *Das kleine Uhr-Symbol erscheint auf erlaubten oder zeitlich beschränkten Abbiegungen. Über dieses Symbol lassen sich zeitlich beschränkte Abbiegeverbote bearbeiten. *Die violette Markierung mit dem Fragezeichen darauf zeigt an, dass alle Abbiegungen am Ende des Segments noch nicht von einem Editor gesperrt resp. bestätigt wurden. *Der runde, grüne Pfeil zeigt die U-Turns an. Wo die Pfeile erscheinen, hängt von der Straßenart ab. Einbahnstraßen haben nur am Ende welche und Straßen ohne Fahrtrichtung haben gar keine. * Mit der Taste '''s''' splittet man überlappende Pfeile auseinander. * Die Taste '''a''' schaltet die Pfeile auf transparent, damit man auch darunter arbeiten kann. * Mit '''Shift+z''' kann man sich alle Abbiegeverbote im Kartenausschnitt anzeigen lassen. Wenn man eine Kreuzung auswählt, öffnet sich der Dialog im Eigenschafts-Fenster links und man kann alle Abbiegungen zulassen oder verbieten abhängig von den Abbiegeverboten der Kreuzung. * Mit der Taste '''w''' erlaubt man alle Abbiegungen. * Mit der Taste '''q''' verbietet man alle Abbiegungen. <br> '''Lies unbedingt die Seite:''' [[Soft und Hard Turns]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==U-Turns bei Sackgassen== Wie eine Sackgasse aussieht findest Du hier: [[Kreuzungen#Sackgassen|Sackgassen]] Die U-Turn-Pfeile am Ende von Sackgassen werden zurzeit im Editor nicht mehr angezeigt. Waze überarbeitet das Routing von U-Turns gerade, und wir wurden gebeten, U-Turns am Ende von Sackgassen nicht mehr zu verändern (was mit WME-Bordmitteln auch nicht mehr geht). Denke auch daran, eine Sackgasse hat immer ein einzelnes zweispuriges Segment. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Mehrfach-Auswahl== Manche Bearbeitungsschritte erfordern eine Mehrfach-Auswahl der Segmente. Diese macht man mit: *'''Mac''': Command + Klick *'''Linux''': Strg + Klick *'''Windows''': Strg + Klick ''Strg-Taste halten und mehrere Segmente auswählen.'' '''Mehrfach-Auswahl dauerhaft aktivieren:''' Mit der Taste '''m''' startet man die Mehrfach-Auswahl. Während man in diesem Modus arbeitet, muss man die Strg-Taste nicht mehr drücken. Will man den Modus beenden, muss man nochmals die Taste '''m''' drücken. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreisverkehr erstellen== # Fahre mit der Maus auf das Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Kreisverkehr''' aus. # Klicke mit der Maus in die Mitte eines Kreisverkehrs. # Bewege die Maus von innen nach außen, um den Kreisverkehr zu vergrößern. # Klicke nochmals und beende das Einzeichnen des Kreisverkehrs. * Kreisverkehre werden standardmäßig rund gezeichnet. Ein Oval kann zusätzlich mit der '''Shift''' Taste während des Einzeichnens erreicht werden. * Kreisverkehre können nur über Kreuzungen oder Segmente gezeichnet werden. Alle Straßen innerhalb des Kreisverkehrs werden gekürzt, und alle Verbindungen innerhalb des Kreisverkehrs werden gelöscht. * Wenn man einen Kreisverkehrs löschen will, müssen alle Segmente gelöscht werden. Er kann nicht gespeichert werden, wenn noch einzelne Segmente vorhanden sind. Die zentralen Kreuzungen werden dabei auch gleich entfernt. Lies hier, wie ein [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehr]] entsteht. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Einen Orientierungspunkt erstellen== # Fahre mit der Maus auf das Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Orientierungspunkt''' aus. # Klicke an einen Punkt an einer Ecke eines Punktes, denn Du darstellen willst. # Bewege die Maus den Umrissen entlang, mit jedem Klick wird ein Geometriepunkt erstellt. # Doppelklick beendet das Einzeichnen. # Wähle den Orientierungspunkt aus, definiere einen Typ und füge eine Beschreibung hinzu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Brücken== # Wähle zwei Segmente aus. # Klick auf das Brückensymbol, das erscheint über der Kreuzung [[Image:Bridge idle.png]]. * Das Brückensymbol erscheint nicht, wenn die zwei Segmente nicht die selben Eigenschaften besitzen. * Die Brückenfunktion erhöht die Segment-Ebene automatisch um eine Stufe höher als das höchste der beiden Segmente. Haben beide Ebene 0, wird daraus Ebene 1. Man kann diese natürlich manuell wieder anpassen. * Für mehr Informationen lies [[Unterführungen und Brücken]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung erstellen== Es gibt keine Funktion zum Erstellen der Kreuzungen. Der Karteneditor generiert die Kreuzungen automatisch und verbindet die Straßen, sobald zwei Straßen aneinandergeführt werden. * Für mehr Informationen lies [[#Ein Segment teilen|Ein Segment teilen]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung löschen== Eine Kreuzung ist ein kleiner blauer Punkt welcher Straßen miteinander verbindet. Kreuzungen können auf drei Arten gelöscht werden: # Wähle die Kreuzung aus und klicke auf das Papierkorb-Symbol oben rechts oder lösche sie mit der Taste "Delete". # Verschiebe eine einzelne Straße mit einer Kreuzung an ihrem Ende, die Kreuzung am Ende löscht sich automatisch. # Wähle mit Ctrl+links Klick zwei Segmente auf beiden Seiten einer Kreuzung aus und Klicke auf das Brückensymbol. Der Level erhöht sich auf Level 1. Wie hier besschrieben [[Unterführungen und Brücken]], müssen beide Segmente die gleichen Attribute besitzen, sonst kann nicht gelöscht werden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung an Schnittpunkten erstellen== Zwei Straßen, die sich kreuzen oder berühren und den gleichen Level haben, können miteinander verbunden werden: # Beide Segmente auswählen. # Klick auf das Icon [[Image:Node idle.png]]. # Eine Kreuzung wird hinzugefügt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzungen vereinen== Kreuzungen können miteinander vereint werden, indem man eine Kreuzung auf eine andere zieht. Auch während einer Mehrfach-Auswahl können Kreuzungen verschoben und vereint werden. Es ist auch möglich, zwei Kreuzungen miteinander zu vereinen, selbst wenn daran Straßen hängen. * Wenn Geometriepunkte auf einem Teilstück liegen und beim Speichern eine Fehlermeldung erscheint, kontrollieren und die Geometriepunkte löschen. Danach nochmals speichern. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==End-Kreuzung verschieben== Jede Straße, die als Sackgasse endet, muss eine Kreuzung am Ende des Segments besitzen, damit sauber aus der Straße herausnavigiert werden kann. Wenn an einem Segment eine End-Kreuzung hängt und man die Kreuzung erhalten will, muss man die Kreuzung auswählen und damit das Segment verschieben. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ein Segment teilen== Es gibt drei Möglichkeiten, [[#Ein Segment teilen|ein Segment zu teilen]] oder eine Kreuzung in der Mitte eines Segments zu platzieren: * Ein neues Segment an den Ort ziehen, wo die Straße geteilt werden soll. Dabei entsteht eine Kreuzung. Nicht benötigte Straße danach löschen. * Ein neues Segment vom Ort wegziehen, wo die Straße geteilt werden soll. Dabei entsteht eine Kreuzung. Nicht benötigtes danach löschen. * Trenne ein Segment am Ende ab. Verbinde ein neues vom Endpunkt des Segments, das getrennt wurde mit der Kreuzung, von der das Segment abgetrennt wurde. Bei all diesen Schritten bleibt die automatisch hinzugefügte Kreuzung bestehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen abtrennen== Segment auswählen und am Ende wegziehen von der Kreuzung, von der es getrennt werden soll. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ganzen Straßenzug auswählen== # Ein Segment auswählen. # Im Eigenschaftsfenster links auf die Schalfläche "Gesamte Straße auswählen" klicken. # Jedes Segment, das mit dem ausgewählten verbunden ist, die gleichen Eigenschaften besitzt wird ausgewählt und kann als Gruppe bearbeitet werden. oder # Ein Segment auswählen # mit gedrückter ALT-Taste ein anderes Segment auswählen # Die Segmente zwischen dem Ersten und Zweiten werden automatisch ausgewählt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Tastaturkürzel== Im Folgenden sind die Standard-Tastaturkürzel erklärt. Du kannst einige Tastenkombinationen anpassen, indem Du mit der Taste "?" die Tastaturkürzel aufrufst. Klick auf einen Eintrag in der Tabelle und danach die Taste oder Kombination auf der Tastatur, die Du dafür verwenden willst. Dies wirkt sich nur auf den aktuellen Browser und Computer aus. Diese Informationen sind nicht auf dem Server gespeichert, Du musst dies für jeden Computer und Browser, den Du verwendest wiederholen. '''Allgemeine Tastaturkürzel'''<br> * '''?''' (oder '''Shift+/ oder Shift+# oder Shift+- oder Shift+~ oder Shift+ù''') zeigt die Tatstaturkürzel an. * '''Delete (Del''') - “Delete“ löscht ein ausgewähltes Segment oder eine Kreuzung. Bei Mehrfach-Auswahl muss man das Papierkorblogo anwählen. * '''Esc''' - “Esc“ verwirft alle Auswahlen. * '''Ctrl+s''' - Speichern ('''Cmd+s''' geht auch für ''Mac'') * '''f''' - Mit der Taste f gelangst Du direkt ins Suchfeld des Karteneditors. '''Kartennavigation'''<br> * '''Shift+UpArrow''' Kartenausschnitt um eine Stufe vergrößern * '''Shift+DownArrow''' Kartenausschnitt um eine Stufe verkleinern * '''Pfeiltasten''' Verschiebt den Kartenausschnitt in alle 4 Richtungen * '''Shift+click''' und '''Doppel-Klick''' - Zentriert den Kartenausschnitt an dem Punkt, wo man hinklickt und vergrößert um eine Stufe. * '''Shift+f''' - Schaltet den Karteneditor auf Vollbild um. * '''Shift+d''' - Leuchtet unbenannte Segmente aus. * '''Alt+c''' - Steuert das Chat-Fenster * '''Shift+c''' - Steuert die Benutzer auf der Karte '''Bearbeitung'''<br> * '''d''' - Löscht einen Punkt der Straßengeometrie, sobald die Geometrie bearbeitet wird und der gewünschte Punkt mit der Maus berührt wird. * '''r''' - Ändert die Richtung eines ausgewählten Segments (es folgt dabei der Reihenfolge des Benennungsdialogs unter dem Eintrag "Richtung") * '''Ctrl+z''' - Rückgängig machen ('''Cmd+z''' geht auch für ''Mac'') * '''Ctrl+Shift+y''' - Wiederholen ('''Cmd+Shift+y''' geht auch für ''Mac'') * '''Ctrl+Shift+z''' - Wiederholen ('''Cmd+Shift+z''' geht auch für ''Mac'') * '''Ctrl+Pfeil nach oben''' - Erhöht die Segment-Ebene, sofern alle ausgewählten Segmente die gleiche Ebene besitzen * '''Ctrl+Pfeil nach unten''' - Verringert die Segment-Ebene, sofern alle ausgewählten Segmente die gleiche Ebene besitzen '''Segment-Operationen'''<br> * '''e''' - Wenn ein Segment ausgewählt ist, steuert dies den Edit-Modus (Edit-Button) * '''h''' - Wenn ein Segment ausgewählt ist, öffnet dies das Fenster für das Bearbeiten der Hausnummern. * '''m''' - Multi Auswahl Modus. Auf der Map kann man, wenn man die m-Taste gedrückt hat mehrere Segmente auswählen. Dies gilt solange bis die m-Taste nochmal gedrückt wird, auch können während einer mehrfach Auswahl Kreuzungen verschoben werden. * '''t''' - Öffnet den Dialog zum Bearbeiten von zeitlich beschränkten Fahrverboten für das ausgewählte Segment. * '''Ctrl+a''' - Wählt die gesamte Straße aus '''Kreuzungen und Abbiegungen'''<br> * '''a''' - Macht die Pfeile der Richtungsangabe transparent, wenn eine Straße ausgewählt ist. Damit nicht Geometriepunkte überlagert werden und man trotzdem an den Straßen neben Kreuzungen arbeiten kann. Dies gilt solange bis die a-Taste nochmal gedrückt wird. * '''s''' - Splittet die Pfeile der Richtungsangabe auseinander, wenn diese übereinander liegen. Hilfreich bei komplizierten Kreuzungen. * '''Shift+z''' - Alle Abbiegeverbote anzeigen ''für jedes Segment''. Keine grünen Pfeile werden angezeigt. * '''q''' - Alle Abbiegungen verbieten für die ausgewählte Kreuzung * '''w''' - Alle Abbiegungen erlauben für die ausgewählte Kreuzung. '''Neu einzeichnen'''<br> * '''i''' - Zeichnet eine neue Straße. * '''o''' - Zeichnet einen neuen Kreisverkehr. '''Ebenen zuschalten'''<br> * '''Shift+a''' Steuert Area-Manager * '''Shift+b''' Steuert Luftaufnahmen * '''Shift+c''' Steuert Städte * '''Shift+r''' Steuert Straßen * '''Shift+g''' Steuert GPS-Punkte * '''Shift+l''' Steuert Orientierungspunkte * '''Shift+s''' Steuert Blitzer * '''Shift+p''' Steuert Kartenfehler * '''Shift+u''' Steuert Aktualisierungsanfragen * '''Shift+e''' Steuert Meine Gebiete </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tips und Tricks= ==Geometrie-Punkte schnell entfernen== Wenn ein Segment ausgewählt ist, bewege die Maus auf die Straße, um die Geometrie-Punkte sichtbar zu machen. Wenn Du einen der Punkte mit der Maus berührst kannst Du ihn mit '''d''' löschen. Wenn Du die '''d'''-Taste hältst, kannst Du mit der Maus einfach der Straße entlang fahren, um alle Geometrie-Punkte zu löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen ohne Namen und Stadt erfassen== * Um Straßen ohne Stadt und Straßennamen zu erfassen, musst Du das Kontrollkästchen "Ohne" für diese Felder benutzen. In Deutschland werden mit Ausnahme der Autobahnen (und deren Zu-/Abfahrtsrampen) alle Segmente mit dem zugehörigen Stadt-/Gemeindenamen benannt. * Neu gezeichnete Straßen können zwar gespeichert werden, bleiben aber rot auf der Karte. * Eine neu gezeichnete Straße kann nicht mit sich selbst verbunden werden, Du musst ein zusätzliches Segment oder Kreuzung hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Geometrie Änderungen bei Mehrfach-Auswahl== Du kannst auch mehrere Straßen auswählen und die Geometrie verändern. Fahre einfach mit der Maus auf die Straße, die Du gerade verändern möchtest. Die Auswahl der anderen Straßen bleibt bestehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Bearbeiten von Kreuzungen legt diese eindeutig fest== In Gegenden mit Base Map gibt es einen Unterschied zu Kreuzungen die vom User bearbeitet oder geupdatet wurden und den Base Map Kreuzungen, die nie bearbeitet/befahren und mit dem Base Map Upload Prozess erstellt wurden. Diese Kreuzungen erscheinen als wären die Abbiegungen verboten, sie können jedoch geroutet werden als ob sie erlaubt wären. In der Regel bevorzugt der Routing Algorithmus Segmente und Kreuzungen, die vom User gesetzt wurden. Aber falls der Weg viel länger oder keiner vorhanden ist wird trotzdem auch über nicht eindeutig gesetzte Abbiegungen geroutet. Eine Straße in beiden Richtungen befahrbar machen ändert nicht den Status der Kreuzung. Wird eine Kreuzung bearbeitet, ist sie gültig, wie in Gegenden ohne Base Map. Die Kreuzung wird nicht gelockt, wenn nur eine Abbiegung geändert wird. <br> Diskussion darüber [http://www.waze.com/forum/viewtopic.php?f=186&t=10319] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Verschieben von Segmenten über die Grenze des Möglichen== Wenn Du das Ende eines Segments zuweit von seinem Start- oder Endpunkt aus verschiebst, wird die Fehlermeldung erscheinen: Das markierte Element wurde über die zulässige Distanz hinaus verschoben. Bitte prüfen und erneut versuchen." Möglichkeiten um dies zu umgehen: * Verschiebe das Segment nur ein wenig und speichere zwischendurch. * Teile das Segment in mehrere Teile auf. * Zeichne ein neues Segment, dieses kannst Du so weit in die Länge ziehen, wie Du willst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Städte-Polygone== Die Städte-, Orts- oder City Polygone enthalten oder umfassen ca. 90-95% aller Straßen, denen der gleiche Stadtname zugeordnet ist. Waze entfernt etwa 5-10% der farbigen Fläche im WME, um grössere Überlappungen zu vermeiden und eine saubere Darstellung zu gewährleisten. Bei der Benennung von neuen Segmenten beträgt der Radius 25 Kilometer zum bestehenden Polygon. Wird ein bereits existierender Stadtname weiter als 25 Kilometer entfernt hinzugefügt erscheint die Meldung: "Die markierte Straße ist zu weit von der zugehörigen Stadt entfernt." </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Blitzer== Der letzte Benutzer, der einen Blitzer bearbeitet hat sperrt diesen auf seinen Rang. Ein Benutzer mit tieferem Rang kann den Blitzer nicht ändern oder löschen, sofern er nicht der Besitzer (Melder) oder Area Manager ist. * Der Blitzer muss in Fahrtrichtung ausgerichtet werden (von der Mitte des Blitzer Icons bis zum Roten Punkt auf der Straße). Das heisst: Er muss so ausgerichtet sein, als ob er von hinten blitzen würde. * Das 30er Schild auf dem Icon beschreibt nicht die Geschwindigkeit, es gehört einfach zum Icon. * Die Waze-App warnt Akustisch, wenn der Blitzer korrekt bestätigt wurde am Waze Map-Editor, in die gleiche Richtung zeigt wie das Straßen Segment, und der Fahrer die Geschwindigkeit überschreitet, die im Blitzer definiert wurde. * Die Waze-App warnt, wenn ein Rotlicht-Blitzer korrekt bestätigt wurde am Waze Map-Editor und in die gleiche Richtung zeigt wie das Straßen Segment. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] c63adf132046115804184227ea1c9e3cc4c58876 12005 12004 2017-10-29T20:43:28Z Popel22 24 /* Blitzer */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Einleitung== Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Man kann alle Objekte auf der Karte beliebig weiter bearbeiten oder löschen. Das gewünschte kann jeweils mit einem Klick ausgewählt und nach Belieben verändert werden. Was mit jedem Objekt oder Segment alles möglich ist, unterscheidet sich nach dem Typ des jeweiligen Objekts und den Rechten des Benutzers. Lies [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] bevor Du loslegst und alles andere findest Du hier in den [[Anleitung_zum_Bearbeiten_der_Karte|Anleitungen]]. ==Anmeldung im Karteneditor== * https://www.waze.com/de/editor/ Melde Dich mit Deinem Benutzernamen und Passwort an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Gebräuchliche Funktionen= ==Die Ebenen== Anzeigen oder verbergen über das Symbol [[Image:Layers-Auswahl.png]] in der oberen, rechten Ecke der Karte. * Mehr Informationen über die Ebenen findest Du hier: [[Der_Waze_Map-Editor#Ebenen-Auswahl|Beschreibung der Ebenen]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Luftaufnahmen== Kann über die Ebene ausgeschaltet werden. Ebenso können GPS-Punkte, Straßen, Orientierungspunkte etc. über die Ebenen gesteuert werden. Du kannst auch an den Straßen arbeiten, wenn die Ebene der Luftaufnahmen ausgeschaltet ist. So kannst Du Straßen anhand der GPS-Punkte ausrichten auf der Karte. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Eine Straße einzeichnen== # Fahre mit der Maus auf dieses Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Straße''' aus. # Klicke in der Karte auf die Stelle, wo du mit dem Einzeichnen beginnen willst. # Ziehe so die Straße an das gewünschte Ende. Jeder Klick dazwischen erstellt einen Geometriepunkt zum Bearbeiten. # Beende mit einem Doppelklick an der Stelle, wo Du mit dem Einzeichnen aufhören willst. * Bevor die Straße oder ein Kreisverkehr auf der Karte erscheint, musst Du speichern. * Für mehr Informationen, lies [[Erstellen und bearbeiten eines Segments]]. Während Du eine neue Straße einzeichnest, kannst Du den Kartenausschnitt mit der linken Maustaste verschieben, bevor Du mit dem Doppelklick das Einzeichnen beendest. Eine neu eingezeichnete Straße wird auf der Karte gleich dargestellt, wie beim Aufzeichnen über die App. Das heißt: Einbahn in Fahrtrichtung rot. Dies ändert sich erst, wenn Du die Straße benannt resp. ihre Eigenschaften bearbeitet hast. Solange Du an Kreuzungen oder Straßen arbeitest, färben sie sich unterschiedlich, bis Du die Änderungen gespeichert hast. So hast Du immer den Überblick, welche Arbeiten noch nicht gespeichert wurden und woran Du gerade gearbeitet hast. '''Eine wichtige Regel Lautet:'''<br> Ein [[Glossar#Segment_oder_Segmente|Segment]] kann niemals mit sich selbst verbunden werden! Eine Straße kann zwar rund gezeichnet werden, aber es entsteht keine Kreuzung, wenn sie sich selbst berührt. '''Bearbeitung ohne Anzeige der Straßen'''<br> Du kannst Straßen und Kreuzungen auch bearbeiten, wenn die Anzeige in der Straßen-Ebene ausgeschaltet ist. Wenn die Ebene der Luftaufnahmen eingeschaltet ist, siehst Du immer noch die Karte. Wenn Du mit der Maus über die verborgenen Straßen fährst, leuchten diese auf. Das Gleiche gilt für Kreuzungen. So kannst Du bequem Straßen an die Karte anpassen oder die GPS-Punkte, wenn der GPS-Layer angeschaltet ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen verbinden== Wenn eine Straße an eine andere geführt wird, verbindet sie sich automatisch durch eine Kreuzung. # Eine neue Straße verbindet sich automatisch mit bereits bestehenden Straßen, wenn man sie aneinanderführt. # Wenn bereits bestehende Straßen am ihrem Ende an eine andere Straße geführt werden, verbinden sie sich automatisch miteinander durch eine Kreuzung. # Wird eine Straße mit einer Kreuzung am Ende an eine andere Straße hingeführt verbindet sich die Kreuzung mit dem bestehenden Segment. An der Kreuzung ziehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen-Schlaufen== Wenn eine Straße eingezeichnet wird, die an beiden Enden das gleiche Segment berührt, wird nur die Kreuzung am Ende der neu eingezeichneten Straße erstellt. Um die Anfangs-Kreuzung zu erstellen: # Das Ende des Segments wegziehen. # Das Segment deselektieren (eine freie Stelle in der Karte anklicken). # Das Segment nochmals auswählen und an die gewünschte Stelle ziehen. Wenn ein Segment gezeichnet wird, das den Anfangs- und Endpunkt auf der selben [[Kreuzungen#Schlaufen|Kreuzung]] hat, funktioniert das obige nicht, und falls doch, sind die Abbiegungen an der Kreuzung falsch. Dieses Segment muss dann durch eine Kreuzung [[#Ein Segment teilen|unterbrochen]] und alle Segmente einzeln verbunden werden. Danach die Abbiegeverbote nicht vergessen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Abbiegungen== Abbiegungen werden über die Verbindungspfeile am Ende jedes verbundenen Segments gesteuert. [[Image:lotsa_turns.jpg|center|frame]] *Rot bedeutet abbiegen verboten, grün bedeutet abbiegen erlaubt in der Richtung, in die die Pfeile zeigen. Wenn ein Pfeil angeklickt wird, ändert dies die Abbiegung von Erlaubt auf Verboten und umgekehrt. Beim Neueinzeichnen einer Straße sind die Pfeile generell rot. *Der rote Pfeil hat an der Spitze ein kleines -, um Farbenblinden die Bearbeitung zu erleichtern. *Der gelbe Pfeil zeigt zeitlich beschränkte Abbiegeverbote an. *Das kleine Uhr-Symbol erscheint auf erlaubten oder zeitlich beschränkten Abbiegungen. Über dieses Symbol lassen sich zeitlich beschränkte Abbiegeverbote bearbeiten. *Die violette Markierung mit dem Fragezeichen darauf zeigt an, dass alle Abbiegungen am Ende des Segments noch nicht von einem Editor gesperrt resp. bestätigt wurden. *Der runde, grüne Pfeil zeigt die U-Turns an. Wo die Pfeile erscheinen, hängt von der Straßenart ab. Einbahnstraßen haben nur am Ende welche und Straßen ohne Fahrtrichtung haben gar keine. * Mit der Taste '''s''' splittet man überlappende Pfeile auseinander. * Die Taste '''a''' schaltet die Pfeile auf transparent, damit man auch darunter arbeiten kann. * Mit '''Shift+z''' kann man sich alle Abbiegeverbote im Kartenausschnitt anzeigen lassen. Wenn man eine Kreuzung auswählt, öffnet sich der Dialog im Eigenschafts-Fenster links und man kann alle Abbiegungen zulassen oder verbieten abhängig von den Abbiegeverboten der Kreuzung. * Mit der Taste '''w''' erlaubt man alle Abbiegungen. * Mit der Taste '''q''' verbietet man alle Abbiegungen. <br> '''Lies unbedingt die Seite:''' [[Soft und Hard Turns]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==U-Turns bei Sackgassen== Wie eine Sackgasse aussieht findest Du hier: [[Kreuzungen#Sackgassen|Sackgassen]] Die U-Turn-Pfeile am Ende von Sackgassen werden zurzeit im Editor nicht mehr angezeigt. Waze überarbeitet das Routing von U-Turns gerade, und wir wurden gebeten, U-Turns am Ende von Sackgassen nicht mehr zu verändern (was mit WME-Bordmitteln auch nicht mehr geht). Denke auch daran, eine Sackgasse hat immer ein einzelnes zweispuriges Segment. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Mehrfach-Auswahl== Manche Bearbeitungsschritte erfordern eine Mehrfach-Auswahl der Segmente. Diese macht man mit: *'''Mac''': Command + Klick *'''Linux''': Strg + Klick *'''Windows''': Strg + Klick ''Strg-Taste halten und mehrere Segmente auswählen.'' '''Mehrfach-Auswahl dauerhaft aktivieren:''' Mit der Taste '''m''' startet man die Mehrfach-Auswahl. Während man in diesem Modus arbeitet, muss man die Strg-Taste nicht mehr drücken. Will man den Modus beenden, muss man nochmals die Taste '''m''' drücken. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreisverkehr erstellen== # Fahre mit der Maus auf das Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Kreisverkehr''' aus. # Klicke mit der Maus in die Mitte eines Kreisverkehrs. # Bewege die Maus von innen nach außen, um den Kreisverkehr zu vergrößern. # Klicke nochmals und beende das Einzeichnen des Kreisverkehrs. * Kreisverkehre werden standardmäßig rund gezeichnet. Ein Oval kann zusätzlich mit der '''Shift''' Taste während des Einzeichnens erreicht werden. * Kreisverkehre können nur über Kreuzungen oder Segmente gezeichnet werden. Alle Straßen innerhalb des Kreisverkehrs werden gekürzt, und alle Verbindungen innerhalb des Kreisverkehrs werden gelöscht. * Wenn man einen Kreisverkehrs löschen will, müssen alle Segmente gelöscht werden. Er kann nicht gespeichert werden, wenn noch einzelne Segmente vorhanden sind. Die zentralen Kreuzungen werden dabei auch gleich entfernt. Lies hier, wie ein [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehr]] entsteht. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Einen Orientierungspunkt erstellen== # Fahre mit der Maus auf das Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Orientierungspunkt''' aus. # Klicke an einen Punkt an einer Ecke eines Punktes, denn Du darstellen willst. # Bewege die Maus den Umrissen entlang, mit jedem Klick wird ein Geometriepunkt erstellt. # Doppelklick beendet das Einzeichnen. # Wähle den Orientierungspunkt aus, definiere einen Typ und füge eine Beschreibung hinzu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Brücken== # Wähle zwei Segmente aus. # Klick auf das Brückensymbol, das erscheint über der Kreuzung [[Image:Bridge idle.png]]. * Das Brückensymbol erscheint nicht, wenn die zwei Segmente nicht die selben Eigenschaften besitzen. * Die Brückenfunktion erhöht die Segment-Ebene automatisch um eine Stufe höher als das höchste der beiden Segmente. Haben beide Ebene 0, wird daraus Ebene 1. Man kann diese natürlich manuell wieder anpassen. * Für mehr Informationen lies [[Unterführungen und Brücken]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung erstellen== Es gibt keine Funktion zum Erstellen der Kreuzungen. Der Karteneditor generiert die Kreuzungen automatisch und verbindet die Straßen, sobald zwei Straßen aneinandergeführt werden. * Für mehr Informationen lies [[#Ein Segment teilen|Ein Segment teilen]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung löschen== Eine Kreuzung ist ein kleiner blauer Punkt welcher Straßen miteinander verbindet. Kreuzungen können auf drei Arten gelöscht werden: # Wähle die Kreuzung aus und klicke auf das Papierkorb-Symbol oben rechts oder lösche sie mit der Taste "Delete". # Verschiebe eine einzelne Straße mit einer Kreuzung an ihrem Ende, die Kreuzung am Ende löscht sich automatisch. # Wähle mit Ctrl+links Klick zwei Segmente auf beiden Seiten einer Kreuzung aus und Klicke auf das Brückensymbol. Der Level erhöht sich auf Level 1. Wie hier besschrieben [[Unterführungen und Brücken]], müssen beide Segmente die gleichen Attribute besitzen, sonst kann nicht gelöscht werden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung an Schnittpunkten erstellen== Zwei Straßen, die sich kreuzen oder berühren und den gleichen Level haben, können miteinander verbunden werden: # Beide Segmente auswählen. # Klick auf das Icon [[Image:Node idle.png]]. # Eine Kreuzung wird hinzugefügt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzungen vereinen== Kreuzungen können miteinander vereint werden, indem man eine Kreuzung auf eine andere zieht. Auch während einer Mehrfach-Auswahl können Kreuzungen verschoben und vereint werden. Es ist auch möglich, zwei Kreuzungen miteinander zu vereinen, selbst wenn daran Straßen hängen. * Wenn Geometriepunkte auf einem Teilstück liegen und beim Speichern eine Fehlermeldung erscheint, kontrollieren und die Geometriepunkte löschen. Danach nochmals speichern. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==End-Kreuzung verschieben== Jede Straße, die als Sackgasse endet, muss eine Kreuzung am Ende des Segments besitzen, damit sauber aus der Straße herausnavigiert werden kann. Wenn an einem Segment eine End-Kreuzung hängt und man die Kreuzung erhalten will, muss man die Kreuzung auswählen und damit das Segment verschieben. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ein Segment teilen== Es gibt drei Möglichkeiten, [[#Ein Segment teilen|ein Segment zu teilen]] oder eine Kreuzung in der Mitte eines Segments zu platzieren: * Ein neues Segment an den Ort ziehen, wo die Straße geteilt werden soll. Dabei entsteht eine Kreuzung. Nicht benötigte Straße danach löschen. * Ein neues Segment vom Ort wegziehen, wo die Straße geteilt werden soll. Dabei entsteht eine Kreuzung. Nicht benötigtes danach löschen. * Trenne ein Segment am Ende ab. Verbinde ein neues vom Endpunkt des Segments, das getrennt wurde mit der Kreuzung, von der das Segment abgetrennt wurde. Bei all diesen Schritten bleibt die automatisch hinzugefügte Kreuzung bestehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen abtrennen== Segment auswählen und am Ende wegziehen von der Kreuzung, von der es getrennt werden soll. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ganzen Straßenzug auswählen== # Ein Segment auswählen. # Im Eigenschaftsfenster links auf die Schalfläche "Gesamte Straße auswählen" klicken. # Jedes Segment, das mit dem ausgewählten verbunden ist, die gleichen Eigenschaften besitzt wird ausgewählt und kann als Gruppe bearbeitet werden. oder # Ein Segment auswählen # mit gedrückter ALT-Taste ein anderes Segment auswählen # Die Segmente zwischen dem Ersten und Zweiten werden automatisch ausgewählt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Tastaturkürzel== Im Folgenden sind die Standard-Tastaturkürzel erklärt. Du kannst einige Tastenkombinationen anpassen, indem Du mit der Taste "?" die Tastaturkürzel aufrufst. Klick auf einen Eintrag in der Tabelle und danach die Taste oder Kombination auf der Tastatur, die Du dafür verwenden willst. Dies wirkt sich nur auf den aktuellen Browser und Computer aus. Diese Informationen sind nicht auf dem Server gespeichert, Du musst dies für jeden Computer und Browser, den Du verwendest wiederholen. '''Allgemeine Tastaturkürzel'''<br> * '''?''' (oder '''Shift+/ oder Shift+# oder Shift+- oder Shift+~ oder Shift+ù''') zeigt die Tatstaturkürzel an. * '''Delete (Del''') - “Delete“ löscht ein ausgewähltes Segment oder eine Kreuzung. Bei Mehrfach-Auswahl muss man das Papierkorblogo anwählen. * '''Esc''' - “Esc“ verwirft alle Auswahlen. * '''Ctrl+s''' - Speichern ('''Cmd+s''' geht auch für ''Mac'') * '''f''' - Mit der Taste f gelangst Du direkt ins Suchfeld des Karteneditors. '''Kartennavigation'''<br> * '''Shift+UpArrow''' Kartenausschnitt um eine Stufe vergrößern * '''Shift+DownArrow''' Kartenausschnitt um eine Stufe verkleinern * '''Pfeiltasten''' Verschiebt den Kartenausschnitt in alle 4 Richtungen * '''Shift+click''' und '''Doppel-Klick''' - Zentriert den Kartenausschnitt an dem Punkt, wo man hinklickt und vergrößert um eine Stufe. * '''Shift+f''' - Schaltet den Karteneditor auf Vollbild um. * '''Shift+d''' - Leuchtet unbenannte Segmente aus. * '''Alt+c''' - Steuert das Chat-Fenster * '''Shift+c''' - Steuert die Benutzer auf der Karte '''Bearbeitung'''<br> * '''d''' - Löscht einen Punkt der Straßengeometrie, sobald die Geometrie bearbeitet wird und der gewünschte Punkt mit der Maus berührt wird. * '''r''' - Ändert die Richtung eines ausgewählten Segments (es folgt dabei der Reihenfolge des Benennungsdialogs unter dem Eintrag "Richtung") * '''Ctrl+z''' - Rückgängig machen ('''Cmd+z''' geht auch für ''Mac'') * '''Ctrl+Shift+y''' - Wiederholen ('''Cmd+Shift+y''' geht auch für ''Mac'') * '''Ctrl+Shift+z''' - Wiederholen ('''Cmd+Shift+z''' geht auch für ''Mac'') * '''Ctrl+Pfeil nach oben''' - Erhöht die Segment-Ebene, sofern alle ausgewählten Segmente die gleiche Ebene besitzen * '''Ctrl+Pfeil nach unten''' - Verringert die Segment-Ebene, sofern alle ausgewählten Segmente die gleiche Ebene besitzen '''Segment-Operationen'''<br> * '''e''' - Wenn ein Segment ausgewählt ist, steuert dies den Edit-Modus (Edit-Button) * '''h''' - Wenn ein Segment ausgewählt ist, öffnet dies das Fenster für das Bearbeiten der Hausnummern. * '''m''' - Multi Auswahl Modus. Auf der Map kann man, wenn man die m-Taste gedrückt hat mehrere Segmente auswählen. Dies gilt solange bis die m-Taste nochmal gedrückt wird, auch können während einer mehrfach Auswahl Kreuzungen verschoben werden. * '''t''' - Öffnet den Dialog zum Bearbeiten von zeitlich beschränkten Fahrverboten für das ausgewählte Segment. * '''Ctrl+a''' - Wählt die gesamte Straße aus '''Kreuzungen und Abbiegungen'''<br> * '''a''' - Macht die Pfeile der Richtungsangabe transparent, wenn eine Straße ausgewählt ist. Damit nicht Geometriepunkte überlagert werden und man trotzdem an den Straßen neben Kreuzungen arbeiten kann. Dies gilt solange bis die a-Taste nochmal gedrückt wird. * '''s''' - Splittet die Pfeile der Richtungsangabe auseinander, wenn diese übereinander liegen. Hilfreich bei komplizierten Kreuzungen. * '''Shift+z''' - Alle Abbiegeverbote anzeigen ''für jedes Segment''. Keine grünen Pfeile werden angezeigt. * '''q''' - Alle Abbiegungen verbieten für die ausgewählte Kreuzung * '''w''' - Alle Abbiegungen erlauben für die ausgewählte Kreuzung. '''Neu einzeichnen'''<br> * '''i''' - Zeichnet eine neue Straße. * '''o''' - Zeichnet einen neuen Kreisverkehr. '''Ebenen zuschalten'''<br> * '''Shift+a''' Steuert Area-Manager * '''Shift+b''' Steuert Luftaufnahmen * '''Shift+c''' Steuert Städte * '''Shift+r''' Steuert Straßen * '''Shift+g''' Steuert GPS-Punkte * '''Shift+l''' Steuert Orientierungspunkte * '''Shift+s''' Steuert Blitzer * '''Shift+p''' Steuert Kartenfehler * '''Shift+u''' Steuert Aktualisierungsanfragen * '''Shift+e''' Steuert Meine Gebiete </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tips und Tricks= ==Geometrie-Punkte schnell entfernen== Wenn ein Segment ausgewählt ist, bewege die Maus auf die Straße, um die Geometrie-Punkte sichtbar zu machen. Wenn Du einen der Punkte mit der Maus berührst kannst Du ihn mit '''d''' löschen. Wenn Du die '''d'''-Taste hältst, kannst Du mit der Maus einfach der Straße entlang fahren, um alle Geometrie-Punkte zu löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen ohne Namen und Stadt erfassen== * Um Straßen ohne Stadt und Straßennamen zu erfassen, musst Du das Kontrollkästchen "Ohne" für diese Felder benutzen. In Deutschland werden mit Ausnahme der Autobahnen (und deren Zu-/Abfahrtsrampen) alle Segmente mit dem zugehörigen Stadt-/Gemeindenamen benannt. * Neu gezeichnete Straßen können zwar gespeichert werden, bleiben aber rot auf der Karte. * Eine neu gezeichnete Straße kann nicht mit sich selbst verbunden werden, Du musst ein zusätzliches Segment oder Kreuzung hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Geometrie Änderungen bei Mehrfach-Auswahl== Du kannst auch mehrere Straßen auswählen und die Geometrie verändern. Fahre einfach mit der Maus auf die Straße, die Du gerade verändern möchtest. Die Auswahl der anderen Straßen bleibt bestehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Bearbeiten von Kreuzungen legt diese eindeutig fest== In Gegenden mit Base Map gibt es einen Unterschied zu Kreuzungen die vom User bearbeitet oder geupdatet wurden und den Base Map Kreuzungen, die nie bearbeitet/befahren und mit dem Base Map Upload Prozess erstellt wurden. Diese Kreuzungen erscheinen als wären die Abbiegungen verboten, sie können jedoch geroutet werden als ob sie erlaubt wären. In der Regel bevorzugt der Routing Algorithmus Segmente und Kreuzungen, die vom User gesetzt wurden. Aber falls der Weg viel länger oder keiner vorhanden ist wird trotzdem auch über nicht eindeutig gesetzte Abbiegungen geroutet. Eine Straße in beiden Richtungen befahrbar machen ändert nicht den Status der Kreuzung. Wird eine Kreuzung bearbeitet, ist sie gültig, wie in Gegenden ohne Base Map. Die Kreuzung wird nicht gelockt, wenn nur eine Abbiegung geändert wird. <br> Diskussion darüber [http://www.waze.com/forum/viewtopic.php?f=186&t=10319] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Verschieben von Segmenten über die Grenze des Möglichen== Wenn Du das Ende eines Segments zuweit von seinem Start- oder Endpunkt aus verschiebst, wird die Fehlermeldung erscheinen: Das markierte Element wurde über die zulässige Distanz hinaus verschoben. Bitte prüfen und erneut versuchen." Möglichkeiten um dies zu umgehen: * Verschiebe das Segment nur ein wenig und speichere zwischendurch. * Teile das Segment in mehrere Teile auf. * Zeichne ein neues Segment, dieses kannst Du so weit in die Länge ziehen, wie Du willst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Städte-Polygone== Die Städte-, Orts- oder City Polygone enthalten oder umfassen ca. 90-95% aller Straßen, denen der gleiche Stadtname zugeordnet ist. Waze entfernt etwa 5-10% der farbigen Fläche im WME, um grössere Überlappungen zu vermeiden und eine saubere Darstellung zu gewährleisten. Bei der Benennung von neuen Segmenten beträgt der Radius 25 Kilometer zum bestehenden Polygon. Wird ein bereits existierender Stadtname weiter als 25 Kilometer entfernt hinzugefügt erscheint die Meldung: "Die markierte Straße ist zu weit von der zugehörigen Stadt entfernt." </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Blitzer== Diese Funktion wurde in der Schweiz deaktiviert, da illegal * <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 4232b4a2ba37a63d937a61435298c04cef792480 12006 12005 2017-10-29T20:45:17Z Popel22 24 /* Blitzer */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Einleitung== Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Man kann alle Objekte auf der Karte beliebig weiter bearbeiten oder löschen. Das gewünschte kann jeweils mit einem Klick ausgewählt und nach Belieben verändert werden. Was mit jedem Objekt oder Segment alles möglich ist, unterscheidet sich nach dem Typ des jeweiligen Objekts und den Rechten des Benutzers. Lies [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] bevor Du loslegst und alles andere findest Du hier in den [[Anleitung_zum_Bearbeiten_der_Karte|Anleitungen]]. ==Anmeldung im Karteneditor== * https://www.waze.com/de/editor/ Melde Dich mit Deinem Benutzernamen und Passwort an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Gebräuchliche Funktionen= ==Die Ebenen== Anzeigen oder verbergen über das Symbol [[Image:Layers-Auswahl.png]] in der oberen, rechten Ecke der Karte. * Mehr Informationen über die Ebenen findest Du hier: [[Der_Waze_Map-Editor#Ebenen-Auswahl|Beschreibung der Ebenen]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Luftaufnahmen== Kann über die Ebene ausgeschaltet werden. Ebenso können GPS-Punkte, Straßen, Orientierungspunkte etc. über die Ebenen gesteuert werden. Du kannst auch an den Straßen arbeiten, wenn die Ebene der Luftaufnahmen ausgeschaltet ist. So kannst Du Straßen anhand der GPS-Punkte ausrichten auf der Karte. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Eine Straße einzeichnen== # Fahre mit der Maus auf dieses Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Straße''' aus. # Klicke in der Karte auf die Stelle, wo du mit dem Einzeichnen beginnen willst. # Ziehe so die Straße an das gewünschte Ende. Jeder Klick dazwischen erstellt einen Geometriepunkt zum Bearbeiten. # Beende mit einem Doppelklick an der Stelle, wo Du mit dem Einzeichnen aufhören willst. * Bevor die Straße oder ein Kreisverkehr auf der Karte erscheint, musst Du speichern. * Für mehr Informationen, lies [[Erstellen und bearbeiten eines Segments]]. Während Du eine neue Straße einzeichnest, kannst Du den Kartenausschnitt mit der linken Maustaste verschieben, bevor Du mit dem Doppelklick das Einzeichnen beendest. Eine neu eingezeichnete Straße wird auf der Karte gleich dargestellt, wie beim Aufzeichnen über die App. Das heißt: Einbahn in Fahrtrichtung rot. Dies ändert sich erst, wenn Du die Straße benannt resp. ihre Eigenschaften bearbeitet hast. Solange Du an Kreuzungen oder Straßen arbeitest, färben sie sich unterschiedlich, bis Du die Änderungen gespeichert hast. So hast Du immer den Überblick, welche Arbeiten noch nicht gespeichert wurden und woran Du gerade gearbeitet hast. '''Eine wichtige Regel Lautet:'''<br> Ein [[Glossar#Segment_oder_Segmente|Segment]] kann niemals mit sich selbst verbunden werden! Eine Straße kann zwar rund gezeichnet werden, aber es entsteht keine Kreuzung, wenn sie sich selbst berührt. '''Bearbeitung ohne Anzeige der Straßen'''<br> Du kannst Straßen und Kreuzungen auch bearbeiten, wenn die Anzeige in der Straßen-Ebene ausgeschaltet ist. Wenn die Ebene der Luftaufnahmen eingeschaltet ist, siehst Du immer noch die Karte. Wenn Du mit der Maus über die verborgenen Straßen fährst, leuchten diese auf. Das Gleiche gilt für Kreuzungen. So kannst Du bequem Straßen an die Karte anpassen oder die GPS-Punkte, wenn der GPS-Layer angeschaltet ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen verbinden== Wenn eine Straße an eine andere geführt wird, verbindet sie sich automatisch durch eine Kreuzung. # Eine neue Straße verbindet sich automatisch mit bereits bestehenden Straßen, wenn man sie aneinanderführt. # Wenn bereits bestehende Straßen am ihrem Ende an eine andere Straße geführt werden, verbinden sie sich automatisch miteinander durch eine Kreuzung. # Wird eine Straße mit einer Kreuzung am Ende an eine andere Straße hingeführt verbindet sich die Kreuzung mit dem bestehenden Segment. An der Kreuzung ziehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen-Schlaufen== Wenn eine Straße eingezeichnet wird, die an beiden Enden das gleiche Segment berührt, wird nur die Kreuzung am Ende der neu eingezeichneten Straße erstellt. Um die Anfangs-Kreuzung zu erstellen: # Das Ende des Segments wegziehen. # Das Segment deselektieren (eine freie Stelle in der Karte anklicken). # Das Segment nochmals auswählen und an die gewünschte Stelle ziehen. Wenn ein Segment gezeichnet wird, das den Anfangs- und Endpunkt auf der selben [[Kreuzungen#Schlaufen|Kreuzung]] hat, funktioniert das obige nicht, und falls doch, sind die Abbiegungen an der Kreuzung falsch. Dieses Segment muss dann durch eine Kreuzung [[#Ein Segment teilen|unterbrochen]] und alle Segmente einzeln verbunden werden. Danach die Abbiegeverbote nicht vergessen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Abbiegungen== Abbiegungen werden über die Verbindungspfeile am Ende jedes verbundenen Segments gesteuert. [[Image:lotsa_turns.jpg|center|frame]] *Rot bedeutet abbiegen verboten, grün bedeutet abbiegen erlaubt in der Richtung, in die die Pfeile zeigen. Wenn ein Pfeil angeklickt wird, ändert dies die Abbiegung von Erlaubt auf Verboten und umgekehrt. Beim Neueinzeichnen einer Straße sind die Pfeile generell rot. *Der rote Pfeil hat an der Spitze ein kleines -, um Farbenblinden die Bearbeitung zu erleichtern. *Der gelbe Pfeil zeigt zeitlich beschränkte Abbiegeverbote an. *Das kleine Uhr-Symbol erscheint auf erlaubten oder zeitlich beschränkten Abbiegungen. Über dieses Symbol lassen sich zeitlich beschränkte Abbiegeverbote bearbeiten. *Die violette Markierung mit dem Fragezeichen darauf zeigt an, dass alle Abbiegungen am Ende des Segments noch nicht von einem Editor gesperrt resp. bestätigt wurden. *Der runde, grüne Pfeil zeigt die U-Turns an. Wo die Pfeile erscheinen, hängt von der Straßenart ab. Einbahnstraßen haben nur am Ende welche und Straßen ohne Fahrtrichtung haben gar keine. * Mit der Taste '''s''' splittet man überlappende Pfeile auseinander. * Die Taste '''a''' schaltet die Pfeile auf transparent, damit man auch darunter arbeiten kann. * Mit '''Shift+z''' kann man sich alle Abbiegeverbote im Kartenausschnitt anzeigen lassen. Wenn man eine Kreuzung auswählt, öffnet sich der Dialog im Eigenschafts-Fenster links und man kann alle Abbiegungen zulassen oder verbieten abhängig von den Abbiegeverboten der Kreuzung. * Mit der Taste '''w''' erlaubt man alle Abbiegungen. * Mit der Taste '''q''' verbietet man alle Abbiegungen. <br> '''Lies unbedingt die Seite:''' [[Soft und Hard Turns]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==U-Turns bei Sackgassen== Wie eine Sackgasse aussieht findest Du hier: [[Kreuzungen#Sackgassen|Sackgassen]] Die U-Turn-Pfeile am Ende von Sackgassen werden zurzeit im Editor nicht mehr angezeigt. Waze überarbeitet das Routing von U-Turns gerade, und wir wurden gebeten, U-Turns am Ende von Sackgassen nicht mehr zu verändern (was mit WME-Bordmitteln auch nicht mehr geht). Denke auch daran, eine Sackgasse hat immer ein einzelnes zweispuriges Segment. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Mehrfach-Auswahl== Manche Bearbeitungsschritte erfordern eine Mehrfach-Auswahl der Segmente. Diese macht man mit: *'''Mac''': Command + Klick *'''Linux''': Strg + Klick *'''Windows''': Strg + Klick ''Strg-Taste halten und mehrere Segmente auswählen.'' '''Mehrfach-Auswahl dauerhaft aktivieren:''' Mit der Taste '''m''' startet man die Mehrfach-Auswahl. Während man in diesem Modus arbeitet, muss man die Strg-Taste nicht mehr drücken. Will man den Modus beenden, muss man nochmals die Taste '''m''' drücken. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreisverkehr erstellen== # Fahre mit der Maus auf das Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Kreisverkehr''' aus. # Klicke mit der Maus in die Mitte eines Kreisverkehrs. # Bewege die Maus von innen nach außen, um den Kreisverkehr zu vergrößern. # Klicke nochmals und beende das Einzeichnen des Kreisverkehrs. * Kreisverkehre werden standardmäßig rund gezeichnet. Ein Oval kann zusätzlich mit der '''Shift''' Taste während des Einzeichnens erreicht werden. * Kreisverkehre können nur über Kreuzungen oder Segmente gezeichnet werden. Alle Straßen innerhalb des Kreisverkehrs werden gekürzt, und alle Verbindungen innerhalb des Kreisverkehrs werden gelöscht. * Wenn man einen Kreisverkehrs löschen will, müssen alle Segmente gelöscht werden. Er kann nicht gespeichert werden, wenn noch einzelne Segmente vorhanden sind. Die zentralen Kreuzungen werden dabei auch gleich entfernt. Lies hier, wie ein [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehr]] entsteht. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Einen Orientierungspunkt erstellen== # Fahre mit der Maus auf das Symbol [[Image:Button-hinzufügen.png]] rechts oben und wähle '''Orientierungspunkt''' aus. # Klicke an einen Punkt an einer Ecke eines Punktes, denn Du darstellen willst. # Bewege die Maus den Umrissen entlang, mit jedem Klick wird ein Geometriepunkt erstellt. # Doppelklick beendet das Einzeichnen. # Wähle den Orientierungspunkt aus, definiere einen Typ und füge eine Beschreibung hinzu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Brücken== # Wähle zwei Segmente aus. # Klick auf das Brückensymbol, das erscheint über der Kreuzung [[Image:Bridge idle.png]]. * Das Brückensymbol erscheint nicht, wenn die zwei Segmente nicht die selben Eigenschaften besitzen. * Die Brückenfunktion erhöht die Segment-Ebene automatisch um eine Stufe höher als das höchste der beiden Segmente. Haben beide Ebene 0, wird daraus Ebene 1. Man kann diese natürlich manuell wieder anpassen. * Für mehr Informationen lies [[Unterführungen und Brücken]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung erstellen== Es gibt keine Funktion zum Erstellen der Kreuzungen. Der Karteneditor generiert die Kreuzungen automatisch und verbindet die Straßen, sobald zwei Straßen aneinandergeführt werden. * Für mehr Informationen lies [[#Ein Segment teilen|Ein Segment teilen]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung löschen== Eine Kreuzung ist ein kleiner blauer Punkt welcher Straßen miteinander verbindet. Kreuzungen können auf drei Arten gelöscht werden: # Wähle die Kreuzung aus und klicke auf das Papierkorb-Symbol oben rechts oder lösche sie mit der Taste "Delete". # Verschiebe eine einzelne Straße mit einer Kreuzung an ihrem Ende, die Kreuzung am Ende löscht sich automatisch. # Wähle mit Ctrl+links Klick zwei Segmente auf beiden Seiten einer Kreuzung aus und Klicke auf das Brückensymbol. Der Level erhöht sich auf Level 1. Wie hier besschrieben [[Unterführungen und Brücken]], müssen beide Segmente die gleichen Attribute besitzen, sonst kann nicht gelöscht werden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzung an Schnittpunkten erstellen== Zwei Straßen, die sich kreuzen oder berühren und den gleichen Level haben, können miteinander verbunden werden: # Beide Segmente auswählen. # Klick auf das Icon [[Image:Node idle.png]]. # Eine Kreuzung wird hinzugefügt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Kreuzungen vereinen== Kreuzungen können miteinander vereint werden, indem man eine Kreuzung auf eine andere zieht. Auch während einer Mehrfach-Auswahl können Kreuzungen verschoben und vereint werden. Es ist auch möglich, zwei Kreuzungen miteinander zu vereinen, selbst wenn daran Straßen hängen. * Wenn Geometriepunkte auf einem Teilstück liegen und beim Speichern eine Fehlermeldung erscheint, kontrollieren und die Geometriepunkte löschen. Danach nochmals speichern. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==End-Kreuzung verschieben== Jede Straße, die als Sackgasse endet, muss eine Kreuzung am Ende des Segments besitzen, damit sauber aus der Straße herausnavigiert werden kann. Wenn an einem Segment eine End-Kreuzung hängt und man die Kreuzung erhalten will, muss man die Kreuzung auswählen und damit das Segment verschieben. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ein Segment teilen== Es gibt drei Möglichkeiten, [[#Ein Segment teilen|ein Segment zu teilen]] oder eine Kreuzung in der Mitte eines Segments zu platzieren: * Ein neues Segment an den Ort ziehen, wo die Straße geteilt werden soll. Dabei entsteht eine Kreuzung. Nicht benötigte Straße danach löschen. * Ein neues Segment vom Ort wegziehen, wo die Straße geteilt werden soll. Dabei entsteht eine Kreuzung. Nicht benötigtes danach löschen. * Trenne ein Segment am Ende ab. Verbinde ein neues vom Endpunkt des Segments, das getrennt wurde mit der Kreuzung, von der das Segment abgetrennt wurde. Bei all diesen Schritten bleibt die automatisch hinzugefügte Kreuzung bestehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen abtrennen== Segment auswählen und am Ende wegziehen von der Kreuzung, von der es getrennt werden soll. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ganzen Straßenzug auswählen== # Ein Segment auswählen. # Im Eigenschaftsfenster links auf die Schalfläche "Gesamte Straße auswählen" klicken. # Jedes Segment, das mit dem ausgewählten verbunden ist, die gleichen Eigenschaften besitzt wird ausgewählt und kann als Gruppe bearbeitet werden. oder # Ein Segment auswählen # mit gedrückter ALT-Taste ein anderes Segment auswählen # Die Segmente zwischen dem Ersten und Zweiten werden automatisch ausgewählt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Tastaturkürzel== Im Folgenden sind die Standard-Tastaturkürzel erklärt. Du kannst einige Tastenkombinationen anpassen, indem Du mit der Taste "?" die Tastaturkürzel aufrufst. Klick auf einen Eintrag in der Tabelle und danach die Taste oder Kombination auf der Tastatur, die Du dafür verwenden willst. Dies wirkt sich nur auf den aktuellen Browser und Computer aus. Diese Informationen sind nicht auf dem Server gespeichert, Du musst dies für jeden Computer und Browser, den Du verwendest wiederholen. '''Allgemeine Tastaturkürzel'''<br> * '''?''' (oder '''Shift+/ oder Shift+# oder Shift+- oder Shift+~ oder Shift+ù''') zeigt die Tatstaturkürzel an. * '''Delete (Del''') - “Delete“ löscht ein ausgewähltes Segment oder eine Kreuzung. Bei Mehrfach-Auswahl muss man das Papierkorblogo anwählen. * '''Esc''' - “Esc“ verwirft alle Auswahlen. * '''Ctrl+s''' - Speichern ('''Cmd+s''' geht auch für ''Mac'') * '''f''' - Mit der Taste f gelangst Du direkt ins Suchfeld des Karteneditors. '''Kartennavigation'''<br> * '''Shift+UpArrow''' Kartenausschnitt um eine Stufe vergrößern * '''Shift+DownArrow''' Kartenausschnitt um eine Stufe verkleinern * '''Pfeiltasten''' Verschiebt den Kartenausschnitt in alle 4 Richtungen * '''Shift+click''' und '''Doppel-Klick''' - Zentriert den Kartenausschnitt an dem Punkt, wo man hinklickt und vergrößert um eine Stufe. * '''Shift+f''' - Schaltet den Karteneditor auf Vollbild um. * '''Shift+d''' - Leuchtet unbenannte Segmente aus. * '''Alt+c''' - Steuert das Chat-Fenster * '''Shift+c''' - Steuert die Benutzer auf der Karte '''Bearbeitung'''<br> * '''d''' - Löscht einen Punkt der Straßengeometrie, sobald die Geometrie bearbeitet wird und der gewünschte Punkt mit der Maus berührt wird. * '''r''' - Ändert die Richtung eines ausgewählten Segments (es folgt dabei der Reihenfolge des Benennungsdialogs unter dem Eintrag "Richtung") * '''Ctrl+z''' - Rückgängig machen ('''Cmd+z''' geht auch für ''Mac'') * '''Ctrl+Shift+y''' - Wiederholen ('''Cmd+Shift+y''' geht auch für ''Mac'') * '''Ctrl+Shift+z''' - Wiederholen ('''Cmd+Shift+z''' geht auch für ''Mac'') * '''Ctrl+Pfeil nach oben''' - Erhöht die Segment-Ebene, sofern alle ausgewählten Segmente die gleiche Ebene besitzen * '''Ctrl+Pfeil nach unten''' - Verringert die Segment-Ebene, sofern alle ausgewählten Segmente die gleiche Ebene besitzen '''Segment-Operationen'''<br> * '''e''' - Wenn ein Segment ausgewählt ist, steuert dies den Edit-Modus (Edit-Button) * '''h''' - Wenn ein Segment ausgewählt ist, öffnet dies das Fenster für das Bearbeiten der Hausnummern. * '''m''' - Multi Auswahl Modus. Auf der Map kann man, wenn man die m-Taste gedrückt hat mehrere Segmente auswählen. Dies gilt solange bis die m-Taste nochmal gedrückt wird, auch können während einer mehrfach Auswahl Kreuzungen verschoben werden. * '''t''' - Öffnet den Dialog zum Bearbeiten von zeitlich beschränkten Fahrverboten für das ausgewählte Segment. * '''Ctrl+a''' - Wählt die gesamte Straße aus '''Kreuzungen und Abbiegungen'''<br> * '''a''' - Macht die Pfeile der Richtungsangabe transparent, wenn eine Straße ausgewählt ist. Damit nicht Geometriepunkte überlagert werden und man trotzdem an den Straßen neben Kreuzungen arbeiten kann. Dies gilt solange bis die a-Taste nochmal gedrückt wird. * '''s''' - Splittet die Pfeile der Richtungsangabe auseinander, wenn diese übereinander liegen. Hilfreich bei komplizierten Kreuzungen. * '''Shift+z''' - Alle Abbiegeverbote anzeigen ''für jedes Segment''. Keine grünen Pfeile werden angezeigt. * '''q''' - Alle Abbiegungen verbieten für die ausgewählte Kreuzung * '''w''' - Alle Abbiegungen erlauben für die ausgewählte Kreuzung. '''Neu einzeichnen'''<br> * '''i''' - Zeichnet eine neue Straße. * '''o''' - Zeichnet einen neuen Kreisverkehr. '''Ebenen zuschalten'''<br> * '''Shift+a''' Steuert Area-Manager * '''Shift+b''' Steuert Luftaufnahmen * '''Shift+c''' Steuert Städte * '''Shift+r''' Steuert Straßen * '''Shift+g''' Steuert GPS-Punkte * '''Shift+l''' Steuert Orientierungspunkte * '''Shift+s''' Steuert Blitzer * '''Shift+p''' Steuert Kartenfehler * '''Shift+u''' Steuert Aktualisierungsanfragen * '''Shift+e''' Steuert Meine Gebiete </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tips und Tricks= ==Geometrie-Punkte schnell entfernen== Wenn ein Segment ausgewählt ist, bewege die Maus auf die Straße, um die Geometrie-Punkte sichtbar zu machen. Wenn Du einen der Punkte mit der Maus berührst kannst Du ihn mit '''d''' löschen. Wenn Du die '''d'''-Taste hältst, kannst Du mit der Maus einfach der Straße entlang fahren, um alle Geometrie-Punkte zu löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Straßen ohne Namen und Stadt erfassen== * Um Straßen ohne Stadt und Straßennamen zu erfassen, musst Du das Kontrollkästchen "Ohne" für diese Felder benutzen. In Deutschland werden mit Ausnahme der Autobahnen (und deren Zu-/Abfahrtsrampen) alle Segmente mit dem zugehörigen Stadt-/Gemeindenamen benannt. * Neu gezeichnete Straßen können zwar gespeichert werden, bleiben aber rot auf der Karte. * Eine neu gezeichnete Straße kann nicht mit sich selbst verbunden werden, Du musst ein zusätzliches Segment oder Kreuzung hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Geometrie Änderungen bei Mehrfach-Auswahl== Du kannst auch mehrere Straßen auswählen und die Geometrie verändern. Fahre einfach mit der Maus auf die Straße, die Du gerade verändern möchtest. Die Auswahl der anderen Straßen bleibt bestehen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Bearbeiten von Kreuzungen legt diese eindeutig fest== In Gegenden mit Base Map gibt es einen Unterschied zu Kreuzungen die vom User bearbeitet oder geupdatet wurden und den Base Map Kreuzungen, die nie bearbeitet/befahren und mit dem Base Map Upload Prozess erstellt wurden. Diese Kreuzungen erscheinen als wären die Abbiegungen verboten, sie können jedoch geroutet werden als ob sie erlaubt wären. In der Regel bevorzugt der Routing Algorithmus Segmente und Kreuzungen, die vom User gesetzt wurden. Aber falls der Weg viel länger oder keiner vorhanden ist wird trotzdem auch über nicht eindeutig gesetzte Abbiegungen geroutet. Eine Straße in beiden Richtungen befahrbar machen ändert nicht den Status der Kreuzung. Wird eine Kreuzung bearbeitet, ist sie gültig, wie in Gegenden ohne Base Map. Die Kreuzung wird nicht gelockt, wenn nur eine Abbiegung geändert wird. <br> Diskussion darüber [http://www.waze.com/forum/viewtopic.php?f=186&t=10319] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Verschieben von Segmenten über die Grenze des Möglichen== Wenn Du das Ende eines Segments zuweit von seinem Start- oder Endpunkt aus verschiebst, wird die Fehlermeldung erscheinen: Das markierte Element wurde über die zulässige Distanz hinaus verschoben. Bitte prüfen und erneut versuchen." Möglichkeiten um dies zu umgehen: * Verschiebe das Segment nur ein wenig und speichere zwischendurch. * Teile das Segment in mehrere Teile auf. * Zeichne ein neues Segment, dieses kannst Du so weit in die Länge ziehen, wie Du willst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Städte-Polygone== Die Städte-, Orts- oder City Polygone enthalten oder umfassen ca. 90-95% aller Straßen, denen der gleiche Stadtname zugeordnet ist. Waze entfernt etwa 5-10% der farbigen Fläche im WME, um grössere Überlappungen zu vermeiden und eine saubere Darstellung zu gewährleisten. Bei der Benennung von neuen Segmenten beträgt der Radius 25 Kilometer zum bestehenden Polygon. Wird ein bereits existierender Stadtname weiter als 25 Kilometer entfernt hinzugefügt erscheint die Meldung: "Die markierte Straße ist zu weit von der zugehörigen Stadt entfernt." </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Blitzer== Diese Funktion wurde in der Schweiz deaktiviert, da illegal <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] df95b18274516d8a2cf901a524d6a5a7e1b102bf 0 82 12007 2017-10-29T20:46:16Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Aktualisierungsanfragen= [[Image:Request pin open-high.gif]] ''Diese Informationen entsprechen de…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Aktualisierungsanfragen= [[Image:Request pin open-high.gif]] ''Diese Informationen entsprechen dem momentanen Zustand. Änderungen vorbehalten.'' =Einleitung= Die Aktualisierungsanfragen auch [[Glossar|Update Requests (UR)]] genannt, sind durch die Benutzer generierte Anfragen. Die Wazer melden so Fehler in der Karte, die sie während der Fahrt mit Waze feststellen. Der Mechanismus beinhaltet auch Informationen über die Strecke, die der Benutzer gefahren ist, wie auch über die Strecke die Waze ihm beim Navigieren angeboten hat. Dies erleichtert das Analysieren der Anfrage in vielen Fällen. Speziell, wenn es um fehlerhafte Kreuzungen und falsche Fahrtrichtungen geht. Damit die Aktualisierungsanfragen angezeigt werden, blende die Ebene [[WME_Oberfläche_und_Steuerelemente#Auswahl_der_Ebenen|Aktualisierungsanfragen]] ein. *Hinweis: Was Du sehen kannst hängt von Deinen Rechten ab. Du kannst nur Aktualisierungsanfragen oder Kartenfehler in Deinem bearbeitbaren Gebiet sehen, wenn Du lokaler Editor mit den nötigen Rechten, Area-Manager des betreffenden Gebiets, oder Country-Manager des betreffenden Landes bist. Denke auch daran, wenn Du [[Der_Waze_Map-Editor#Der_Permalink | Permalinks]] im Forum postest. [[Image:FehlerMeldung.png|700px]] =Elemente der Oberfläche= Die Farbe der Kegel - wie bei den [[WME Map Problems|Kartenfehlern]] - haben eine Bedeutung. Im Falle der Aktualisierungsanfragen, ist diese das Alter der Anfrage. Ein Ausrufezeichen im Symbol zeigt, dass die Aktualisierungsanfrage noch offen ist. Ein Häkchen zeigt an, dass sie bearbeitet oder geschlossen wurde. [[Image:Request pin open-low.gif|left]] Ein gelber Kegel ist offen seit 0-5 Tagen.<br clear="all"> [[Image:Request pin open-med.gif|left]] Ein orangefarbener Kegel ist offen seit 6-14 Tagen.<br clear="all"> [[Image:Request pin open-high.gif|left]] Ein roter Kegel ist offen seit mehr als 15 Tagen.<br clear="all"> [[Image:Request pin-notidentified.gif|left]] Der Update Request ändert sich zu diesem Kegel, wenn Du ihn als "Nicht identifiziert" markierst.<br clear="all"> [[Image:Request pin-complete.gif|left]] Die Aktualisierungsanfrage ändert sich zu diesem Kegel, wenn Du das Problem als "Gelöst" markierst.<br clear="all"> Wenn der Kegel zur Anfrage angeklickt wird, öffnet sich zuoberst auf der Karte das Fenster mit den Informationen. In der oberen Leiste des Fensters ist "Benutzermeldung" zu sehen, woran die Anfrage eines Benutzers erkennbar ist. Weiter ist die Art des Fehlers erkennbar, z.B. Allgemeiner Kartenfehler. ===Kartenfehler, die Kommentare enthalten=== Kommentare beinhalten in der Regel Anfragen oder Konversationen zum gemeldeten Fehler. [[Image:Request_pin_open_conversation-low.gif|left]] Ein gelber Kegel ist offen seit 0-5 Tagen und enthält Kommentare.<br clear="all"> [[Image:Request_pin_open_conversation-med.gif|left]] Ein orangefarbener Kegel ist offen seit 6-14 Tagen und enthält Kommentare.<br clear="all"> [[Image:Request_pin_open_conversation-high.gif|left]] Ein roter Kegel ist offen seit mehr als 15 Tagen und enthält Kommentare.<br clear="all"> ===Die Meta-Info=== [[File:Meta Informationen.png]] Links ist eine Beschreibung zu sehen, wenn der Melder einen Text eingegeben hat und das Datum der Anfrage. ===Auswahl von "Fahrt und Route"=== [[File:Fahrt Anzeigen.png]] Auf der rechten Seite sind entweder zwei Kontrollkästchen, nur eines oder auch gar keines zu sehen. Dies ist abhängig von den Daten, die die Waze-App eruieren konnte. Man kann dabei auswählen, welche Route man anschauen möchte, die von Waze vorgeschlagene, die tatsächlich befahrene Strecke oder auch beide (Standard beim Öffnen) zusammen. Mit einem Klick auf den blauen Link "Anzeigen" zoomt der Karteneditor ungefähr zu dem Ort, wo das Problem liegt und vergrößert die Ansicht an den Punkt, an dem die meisten Informationen sichtbar sind. Manchmal muss man auch zoomen oder die Karte verschieben, um alle wichtigen Informationen zur Fahrt zu sehen. [[File:Anzeigen.png]] ===Anzeige-Feld des Fehlers=== Damit man im Kartenausschnitt mehr zu sehen bekommt, kann man das Feld mit der Beschreibung des Fehlers nach oben verkleinern. Klicke dazu auf die Schaltfläche [[File:Weniger.png]] Das Feld bei Verkleinerung: [[Image:Fehler klein.png|700px]] Um das Feld zurück wieder zu vergrößern, klicke auf die Schaltfläche [[File:Mehr.png]] Standard-Ansicht: [[Image:Fehler gross.png|700px]] ===Markieren mit "Melden als"=== [[File:Melden als.png]] Unten kann man die Anfrage mit einer Auswahl entsprechend schließen. Man kann sie: * Offen lassen, wenn man keine Ahnung hat was falsch ist oder die Bearbeitung im Moment nicht möglich ist. * Als "Gelöst" markieren, wenn die Anfrage korrekt bearbeitet wurde und das Problem gelöst ist. * Als "Nicht identifiziert" markieren, wenn kein richtiger Fehler erkennbar ist. ===Fenster schließen=== [[File:Schliessen.png]] Ganz rechts befindet sich der Schließen-Button, mit dem man die Anfrage schließt. Wenn eine der Auswahlen oben getroffen und die Anfrage geschlossen wurde, muss man nur noch Speichern drücken. =Gefahrene und vorgeschlagene Route= Die Strecke, die Waze bei der Navigation vorgeschlagen hat ist lila, wie in der Anwendung. Die Strecke, die der Benutzer tatsächlich gefahren ist, ist grün. Wenn die Richtung nicht zu sehen ist, muss man zoomen. Zusätzlich zur vorgeschlagenen Strecke wird an jeder Kreuzung eine Abbiege-Markierung angezeigt. [[Image:Routen.png]] Abbiege-Markierungen: * [[Image:Big direction forward.png]] - Geradeaus fahren. * [[Image:Big direction right.png]] - Rechts abbiegen. * [[Image:Big direction left.png]] - Links abbiegen * [[Image:Big direction exit right.png]] - Ausfahrt/rechts halten. * [[Image:Big direction exit left.png]] - Ausfahrt/links halten. * [[Image:Big_directions_roundabout.png]] - Kreisverkehr nummerierte Ausfahrt. * [[Image:Big_directions_roundabout_l.png]] - Kreisverkehr links abbiegen. * [[Image:Big_directions_roundabout_r.png]] - Kreisverkehr rechts abbiegen * [[Image:Big_directions_roundabout_s.png]] - Kreisverkehr geradeaus fahren. * [[Image:Big_directions_roundabout_u.png]] - Kreisverkehr "wenden" (Ausfahrt gleich Einfahrt) * Leeres Feld - Fehler an Kreuzung ([[#Leeres Feld|siehe unten]]) =Analyse= ==Strecken-Analyse== Anhand der Informationen aus einer Abweichung der gewünschten Route und der tatsächlich gefahrenen Strecke können Kreuzungen ausfindig gemacht werden, an denen die Abbiegungen verändert werden müssen. ==Analyse der Abbiegungen== ===Orientierung=== Die Pfeile der Abbiege-Markierungen, die der Waze Map-Editor an den Kreuzungen anzeigt, mögen verwirrend erscheinen. Dies liegt daran, dass die Karte eine Nord-Orientierung besitzt. Eine Route die nach Süden führt, zeigt dennoch Die Pfeile so an als würde man nach Norden fahren. *'''Das Wichtigste ist, dass man sich die Abbiegungen (Pfeile) aus Sicht des Fahrers vorstellt.''' ===Geradeaus-Pfeil=== In der Regel gibt die Anwendung während der Navigation keine hörbaren Anweisungen für geradeaus fahren, die Anweisung, die zu hören ist bezieht sich dann auf die nächste Kreuzung. ===Leeres Feld=== Es kann Umstände geben, in denen der Waze Map-Editor ein leeres Feld an einer Kreuzung anzeigt. Dies geschieht, weil der Routing-Server an dieser Kreuzung keine Instruktionen geben konnte. Die Gründe dafür sind: # Mit der Kreuzung ist etwas nicht in Ordnung. #* Ein kurzes Kreis-Segment #* Verzerrtes Segment # Es existert ein Fehler im Routing-Server. Wenn der Grund Nummer 1 ist, ist dies einfach zu beheben am Waze Map-Editor. Wenn nicht, kann es sich um einen Fehler im Routing-Server handeln, in welchem Fall man ein Ticket auf der [http://world.waze.com/support/ Seite "Benutzerunterstützung"] eröffnen sollte. Alternativ dazu kann man auch das [[Diskussionsforum|Forum]] konsultieren oder sich ein Bild auf der [http://status.waze.com/ Status-Seite] darüber verschaffen, ob vielleicht temporäre Server-Probleme bestehen. ==Kommunikation== [[File:wme_ur_conversation1.jpg]] Kommunikation mit dem Melder einer Aktualisierungsanfrage ist in der App und im Editor über die Kommentarfunktion (Unterhaltung) möglich. Neu erstellte URs haben noch keine Kommentare, die Unterhaltung-Schaltfläche zeit "0", bis ein Kommentar eingestellt ist. Die Kommentare ermöglichen Nachfragen an den Melder, und bietet dem Melder die Möglichkeit, Details zum Hintergrund seiner Meldung mitzuteilen. Diese Kommunikation wird fortgesetzt, bis das Problem gelöst oder als nicht lösbar ("nicht identifizert") eingestuft wurde. ===Oberfläche=== [[File:wme_ur_conversation_replies.jpg|210px|right]] Rechts ist beispielhaft eine Unterhaltung mit mehreren Kommentaren von einem Editor und dem Melder dargestellt. Die Unterhaltung-Schaltfläche zeigt die Gesamtanzahl an Kommentaren - vom Melder und von anderen Editoren - dieser Aktualisierungsanfrage. Die Kommentare vom Melder tragen einen blauen Hintergrund, die von anderen Editoren einen weißem Hintergrund. ===Vorgehen=== Die Unterhaltung einer Aktualisierungsanfrage wird durch Anklicken der Unterhaltung-Schaltfläche geöffnet. Ein erneutes Anklicken der Schaltfläche schließt die Unterhaltung wieder, wodurch wieder mehr Raum für die Karte zur Verfügung steht. Ein neuer Kommentar (oder eine neue Frage) wird in das Textfeld '''Kommentar hinzufügen''' eingegeben. Der neue Kommentar wird durch einen Klick auf die Senden-Schaltfläche abgeschickt. Man kann beliebig viele Kommentar eingeben. Nach dem Senden eines Kommentars wird automatisch das Verfolgen der Unterhaltung aktiviert. Durch Anlicken von '''Nicht mehr folgen''' wird dies wieder abgestellt. Details dazu finden sich im Abschnitt [[#Benachrichtigungen|Benachrichtigungen]] weiter unten. Ein abgeschickter Kommentar kann nicht mehr nachbearbeitet oder entfernt werden. Jeder Kommentar ist für alle Editoren sichtbar. Man kann Benachrichtigungen auch für eine Aktualisierungsanfrage aktivieren, welche man nicht kommentiert hat, indem man '''Folge''' anklickt. Durch Anlicken von '''Nicht mehr folgen''' wird dies wieder abgestellt. Jeder Editor, welcher einer Aktualisierungsanfrage folgt, kann Kommentare auch über die Nachricht in der Waze App eingeben, welche er empfängt, sobald die Aktualisierungsanfrage einen neuen Kommentar erhält. Es ist möglich, dass Sie die Fahrt und Routendaten finden. Diese können bei der Lösung der Update-Anfragen, ohne zusätzliche Anfrage beim Melder hilfreich sein ===Benachrichtigungen=== Hier ist eine kurze Zusammenfassung der Meldungen, die das System sendet: *Wenn du der Melder bist #Du erhälst eine Nachricht in der Waze-App im Posteingang wenn ein Editor einen Kommentar zur UR Konversation schreibt. #Du erhälst eine E-Mail und eine Nachricht in der App, wenn ein anderer Editor oder der Melder einen Kommentar schreibt. *Wenn Du die Anforderung begonnen hast (als Editor): #Du erhälst eine E-Mail und eine Nachricht in der der Waze-App wenn ein anderer Editor oder der Melder einen Kommentar anfügt #Du erhälst eine E-Mail und eine Nachricht in der der Waze-App wenn ein anderer Editor den UR mit gelöst oder nicht identifiziert schließt. '''{{Red|Hinweis:}}''' Wenn Sie Ihren eigenen Update Request schließen, erhalten Sie keine In-App-Nachricht oder E-Mail. ===Etiquette (Leitlfaden für den Umgang mit UR- Unterhaltungen)=== Sobald sie einen Kommentar oder eine Frage zu einem UR stellen, die eine Antwort vom Meder des UR's erfordert, wird empfohlen das man (7) Tage auf eine Antwort wartet. Sollte der Melder nicht antworten so kann man nach diesen (7) Tagen eine freundliche Erinnerung an den Melder schreiben. Wenn das Update Request Gespräch keine Updates für mindestens sieben (7) Tage hat, und die Gesamtzeit des UR (14) Tage beträgt, kann der UR mit nicht identifiziert geschlossen werden. '''{{Red|Hinweis:}}''' Nach schließen des UR ist eine Antwort des Melders aus der App evtl. nicht mehr möglich! *Sind sie nicht der ursprüngliche Editor, fügen sie einen Notiz an warum sie den UR geschlossen haben. Diese Nachricht erhalten alle an der Unterhaltung beteiligten. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 49af172f15d66b38f9a061fd1ae755252e6169fc 0 83 12008 2017-10-29T20:46:47Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Kartenfehler= [[Image:New ap icon red.png]] ''Diese Informationen entsprechen dem momentanen Zus…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Kartenfehler= [[Image:New ap icon red.png]] ''Diese Informationen entsprechen dem momentanen Zustand. Änderungen vorbehalten.'' =Einleitung= Die Kartenfehler auch [[Glossar#MP|Map Errors]] genannt, sind durch das System generierte Fehlermeldungen. Das System erkennt Fehler in der Karte, die während der Fahrt mit Waze registriert wurden. Der Mechanismus beinhaltet auch Informationen über die Strecke, die der Benutzer gefahren ist, wie auch über die Strecke die Waze ihm beim Navigieren angeboten hat. Dies erleichtert das Analysieren der Fehler in vielen Fällen. Speziell, wenn es um fehlerhafte Kreuzungen und falsche Fahrtrichtungen geht. Damit die Kartenfehler angezeigt werden, blende die Ebene [[WME_Oberfläche_und_Steuerelemente#Auswahl_der_Ebenen|Kartenfehler]] ein. *Hinweis: Was Du sehen kannst hängt von Deinen Rechten ab. Du kannst nur Aktualisierungsanfragen oder Kartenfehler in Deinem bearbeitbaren Gebiet sehen, wenn Du lokaler Editor mit den nötigen Rechten, Area-Manager des betreffenden Gebiets, oder Country-Manager des betreffenden Landes bist. Denke auch daran, wenn Du [[Der_Waze_Map-Editor#Der_Permalink | Permalinks]] im Forum postest. [[Image:Kartenfehler.png|700px]] =Elemente der Oberfläche= Die Farben der Kegel - wie bei den [[WME_Update_Requests|Aktualisierungsanfragen]] - haben eine spezifische Bedeutung. Bei den Kartenfehlern hängen diese mit der Anzahl der Fahrten über diese Problemstellen zusammen. Je mehr Fahrten, die durch diese Stellen getätigt werden, desto dringender muss das Problem gelöst werden. Ein Ausrufezeichen im Kegel bedeutet, dass das Problem noch offen ist. Ein Häkchen bedeutet, dass das Problem gelöst wurde. [[Image:New_ap_icon_yellow.png|left]] Ein gelber Kegel wurde generiert durch 1-3 Fahrten.<br clear="all"> [[Image:New_ap_icon_orange.png|left]] Ein oranger Kegel wurde generiert durch 4-7 Fahrten.<br clear="all"> [[Image:New_ap_icon_red.png|left]] Ein roter Kegel wurde generiert durch 8 oder mehr Fahrten.<br clear="all"> [[Image:New_ap_icon_green_not_ident.png‎|left]] Der Kegel wird grün und enthält ein Fragezeichen, wenn das Problem nicht gelöst werden konnte und die Anfrage als "Nicht identifiziert" gekennzeichnet wurde. Dies ist bei allen Unklarheiten, die das Lösen des Problems verhindern von Vorteil. Beim Speichern wird eine E-Mail an den Melder versendet mit der Bitte um genauere Infos. <br clear="all"> [[Image:New_ap_icon_green_solved.png|left]] Der Kegel wird grün und enthält ein Häkchen, wenn das Problem gelöst wurde. Wenn ein Problem nicht wirklich ein Problem darstellt (Tunnels, Bahnfahrer etc.), oder anhand schlechter GPS-Daten produziert wurde, dann ist dieses Problem als "Gelöst" zu schließen.<br clear="all"> ===Die Meta-Info=== [[Image:Meta Informationen2.png|700px]] Wenn ein Kartenfehler angeklickt wird, werden im oberen Bereich die Informationen zum Problem angezeigt. Auch wird angezeigt, dass es sich um einen Kartenfehler handelt, der vom System erkannt wurde. ===Auswahl von "Fahrt und Route"=== [[File:Fahrt Anzeigen2.png]] Auf der rechten Seite sind entweder zwei Kontrollkästchen, nur eines oder auch gar keines zu sehen. Dies ist abhängig von den Daten, die die Waze-App eruieren konnte. Man kann dabei auswählen, welche Route man anschauen möchte, die von Waze vorgeschlagene, die tatsächlich befahrene Strecke oder auch beide (Standard beim Öffnen) zusammen. Mit einem Klick auf den blauen Link "Anzeigen" zoomt der Karteneditor ungefähr zu dem Ort, wo das Problem liegt und vergrößert die Ansicht an den Punkt, an dem die meisten Informationen sichtbar sind. Manchmal muss man auch zoomen oder die Karte verschieben, um alle wichtigen Informationen zur Fahrt zu sehen. [[File:Anzeigen2.png]] ===Anzeige-Feld des Fehlers=== Damit man im Kartenausschnitt mehr zu sehen bekommt, kann man das Feld mit der Beschreibung des Fehlers nach oben verkleinern. Klicke dazu auf die Schaltfläche [[File:Weniger.png]] Das Feld bei Verkleinerung: [[Image:Fehler klein2.png|700px]] Um das Feld zurück wieder zu vergrößern, klicke auf die Schaltfläche [[File:Mehr.png]] Standard-Ansicht: [[Image:Fehler gross2.png|700px]] ===Markieren mit "Melden als"=== [[File:Melden als.png]] Unten kann man die Meldung mit einer Auswahl entsprechend schließen. Man kann sie: * Offen lassen, wenn man keine Ahnung hat was falsch ist oder die Bearbeitung im Moment nicht möglich ist. * Als "Gelöst" markieren, wenn die Meldung korrekt bearbeitet wurde und das Problem gelöst ist. * Als "Nicht identifiziert" markieren, wenn kein richtiger Fehler erkennbar ist. ===Fenster schließen=== [[File:Schliessen.png]] Ganz rechts befindet sich der Schließen-Button, mit dem man die Meldung schließt. Wenn eine der Auswahlen oben getroffen und die Meldung geschlossen wurde, muss man nur noch Speichern. =Gefahrene und vorgeschlagene Route= Die Strecke, die Waze bei der Navigation vorgeschlagen hat ist lila, wie in der Anwendung. Die Strecke, die der Benutzer tatsächlich gefahren ist, ist grün. Wenn die Richtung nicht zu sehen ist, muss man zoomen. Zusätzlich zur vorgeschlagenen Strecke wird an jeder Kreuzung eine Abbiege-Markierung angezeigt. Die Zahl im Kreis zeigt an, wie viele Fahrten bereits durch diesen Fehler stattgefunden haben. [[Image:Routen2.png]] =Analyse= ==Vom System erkannte Probleme== * '''Fehlende Straße''' - ''Die Straßen sind zu weit voneinander entfernt und womöglich fehlt eine Straße dazwischen'' (fehlende Straße zwischen zwei Verbindungen). <br>In vielen Fällen handelt es sich um Probleme innerhalb Parkplätzen oder Störungen des GPS. Wenn es keiner Lösung bedarf oder der Fehler kein Fehler ist, schließe den Fehler als "Gelöst" * '''Verbotene Abbiegung könnte erlaubt werden''' - ''Die Route führt durch eine verbotene Abbiegung'' (Abbiegung fehlt).<br>Wähle die Segmente aus in dem Gebiet und kontrolliere die Abbiegungen. Achtung: Vielleicht handelt es sich auch um zeitlich beschränkte Abbiegeverbote. Löse das Problem und schließe es als "Gelöst", auch falls es sich nicht um ein Problem handelt, oder es sich um zeitlich beschränkte Abbiegeverbote handelt. * '''Fahrtrichtungsfehler''' - ''Ein Teil der Route verläuft in falscher Fahrtrichtung'' (falsche Fahrtrichtung eines Segments).<br>Dies kann ein Problem sein oder auch nicht. Kontrolliere die Fahrtrichtung des Segments und ändere sie, wenn es nötig ist. Es kann auch sein, dass sich Fußgänger oder Radfahrer in der falschen Richtung bewegen! * '''Fehlende Kreuzung''' - ''Die Straßen sind nahe beieinander, aber sie sind nicht durch eine Kreuzung verbunden'' (fehlende Verbindung zu einem anderen Segment).<br>Hierbei kann es sich um eine fehlende Kreuzung handeln oder auch um ein schlechtes GPS-Signal. Liegen zwei Straßen nahe beieinander kann es sein, dass der Client den Fahrer hin und her springen lässt, sodass das System glaubt es bestünde eine Verbindung dazwischen. Wenn es keiner Lösung bedarf oder der Fehler kein Fehler ist, schließe den Fehler als "Gelöst" * '''Kreuzung am Schnittpunkt fehlt''' - ''Die Straßen kreuzen einander, jedoch fehlt eine Kreuzung am Schnittpunkt'' (Straßen kreuzen sich, sind aber nicht durch eine Kreuzung verbunden).<br>Dies passiert oft, wenn ein Editor neue Straßen hinzufügt und keine Verbindungen herstellt. Kann auch beim Aufzeichnen von Straßen und Eisenbahnen passieren, daher kontrolliere ob die Verbindungen korrekt sind, * '''Empfohlene Route häufig ignoriert''' - ''Die meisten Benutzer folgten nicht der empfohlenen Route'' (Die Wazer folgen einer anderen, als der vorgeschlagenen Route).<br>Die Nummer im grünen Kreis zeigt an wie viele Fahrten entlang der Route stattgefunden haben. Schau Dich um nach falschen Abbiegungen oder fehlenden Verbindungen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 032ca00f7f7198cc48ac53f83488018ccb07c45b 0 84 12009 2017-10-29T20:47:29Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Übersicht== Waze hat eine eigene interne Datenbank mit Adressen und Hausnummern. Diese Adressen…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Übersicht== Waze hat eine eigene interne Datenbank mit Adressen und Hausnummern. Diese Adressen werden nur dann genutzt, wenn eine bestimmte Adresse im Karteneditor oder in der Waze-App gesucht wird. Die Hausnummern bei Waze sind unabhängig von externen Providern. Die Hausnummern im Karteneditor besitzen Positionspunkte, welche auf der Karte genau so platziert werden können, damit der Benutzer an die richtige Stelle der gewünschten Adresse navigiert wird. Routenende ist der Positionspunkt, der auf der Straße platziert wurde. ==Anmerkungen== * Der Hausnummern-Editor kann nicht aktiviert werden, wenn ungespeicherte Edits vorhanden sind. * Hausnummern können nur bis Zoom-Stufe 20m/100ft und tiefer bearbeitet werden. * Hausnummern können nicht zu unbenannten Segmenten hinzugefügt werden. * Hausnummern können Zahlen und Buchstaben beinhalten. * Ein Straßenname kann nicht entfernt werden, wenn eine Hausnummer zugeordnet ist. ==Editor öffnen== Damit Hausnummern bearbeitet werden können, musst Du ein Segment auswählen und auf die Schaltfläche [[File:Hausnummern.png]] klicken. <br> Oder verwende das Tastaturkürzel: '''H''' ==Arbeiten mit dem Editor== [[Image:Housenumbers wme bigpicture.jpg|right|thumb|Ansicht der Hausnummern und der ausgeleuchteten Segmente.]] Der Hausnummern-Editor leuchtet auch mehrere Segmente mit gleichem Namen aus. Du kannst die Karte verschieben, um an mehreren Straßen als nur der ausgewählten, die Hausnummern hinzuzufügen. <br> Das hell ausgeleuchtete Gebiet um das Segment herum ist die Standard Distanz, innerhalb welcher Du die Hausnummern für Segmente platzieren kannst. Wenn Du eine Nummer außerhalb des ausgeleuchteten Gebiets platzieren willst, musst Du auf die Schaltfläche '''Erzwingen''' klicken damit Du speichern kannst. [[Image:Force.png]] *Merke: Du kannst nur bis zur Zoom-Stufe 20m/100ft und tiefer Hausnummern bearbeiten. Wenn die Zoom-Stufe nicht stimmt erscheint die Meldung [[Image:Zoomin.png]] am oberen Rand des Editors. <br clear="all" /> ===Werkzeugleiste=== Wenn der Hausnummern-Editor aktiviert ist, erscheint eine neue Leiste mit den Werkzeugen, die gebraucht werden, um an den Hausnummern zu arbeiten. [[Image:HausnummernWL.png|700px]] Beschreibung der einzelnen Schaltflächen: [[File:Hinzu.png|left]] Klick auf "Hinzufügen" um eine Hausnummer hinzuzufügen<br clear="all" /> [[File:SpeichernHN.png|left]] Klick auf "Speichern" um die Änderungen zu speichern<br clear="all" /> [[File:Rueckgaengig.png|left]] Klick auf "Rückgängig" um den letzten Schritt rückgängig zu machen<br clear="all" /> [[File:Wiederholen.png|left]] Klick auf "Wiederholen" um den letzten Schrit zu wiederholen<br clear="all" /> [[File:SchliessenHN.png|left]] Klick auf "Schließen" um den Editor zu schließen<br clear="all" /> '''Tastaturkürzel''':<br> *'''Ctrl+S''' Speichern<br> *'''Ctrl+Z''' Rückgängig<br> *'''Ctr+Shift+Z''' Wiederholen<br> *'''Esc''' Editor schließen<br> ===Markierungen=== [[Image:Housenumbers wme number active.gif|right]][[Image:Housenumbers wme number active flip.gif|right]] Die zwei Bilder rechts zeigen, wie die Hausnummern dargestellt werden im Editor. Welcher der beiden verwendet wird ist abhängig von der Lage und der Dichte der Nummern auf einer Straße. * Das rote "X" is der Löschen Button * Der blaue Punkt ist dafür da, um die Nummer mit der Maus zu verschieben Die Hausnummer selbst sollte auf dem Dach eines Hauses platziert werden. Bei grösseren Gebäuden, wie Fachmärkten oder Warenhäusern sollten die Nummern am Eingang des Gebäudes platziert werden. Gibt es in großen Warenhäusern mehrere Hausnummern sollte die Nummer wie bei einem normalen Haus positioniert werden. ===Nummer hinzufügen=== Um eine Nummer hinzuzufügen, ''klick'' auf den '''Hinzufügen''' Button in der Werkzeugleiste. ''Klick'' an den '''Ort''' wo die Nummer positioniert werden soll. ''Füge'' die Nummer hinzu und speichere danach. ===Nummern verändern=== * Um eine Nummer zu bearbeiten, ''klick'' ins Nummernfeld und bearbeite sie. * Um eine Nummer zu verschieben, ''klick'' auf die Nummer und verschieben sie, indem Du am blauen Punkt ziehst. * Um eine Nummer zu löschen, ''klick'' auf die Nummer und dann auf das '''rote X'''. ===Die Segment-Markierung=== Die Segment-Markierung beschreibt den Punkt, wo die Hausnummer hinzugefügt wird und dies ist der Ort, wo die Navigation endet in der Waze-App. Die Markierung wird mit einem weißen Punkt mit blauem Rand dargestellt, der sich auf dem Segment befindet: [[Image:Housenumbers_wme_adjust_stop_point.jpg|center]] Wenn eine Hausnummer verschoben wird erscheint eine weiße Linie, die von der Nummer zur Segment-Markierung (weißer Punkt) auf dem ausgewählten Segment führt. Der Punkt kann überall auf gleichnamigen Segmenten verschoben werden, er kann jedoch nicht auf ein anderes Segment mit einem anderen Namen verschoben werden. Die Segment-Markierung sollte da platziert werden, wo man sein Fahrzeug parkieren würde in der Nähe des Haupteinganges (Zufahrt, Parkplatz, Einfahrt etc.) zu einem Gebäude. Wichtig dabei ist, dem Fahrer zu ermöglichen die gewünschte Nummer zu finden. * Es wird an einer Möglichkeit gearbeitet Hausnummern auch zu unbenannten Segmenten hinzuzufügen. ==Speichern erzwingen== <span style="color:#f00;">'''Hinweis''':</span> Das Erzwingen von Hausnummern beschränkt sich derzeit auf Stufe 3 Editoren und höher. Waze wird hier noch Anpassungen vornehmen, vor allem in Ländern, in denen ein einheitliches Muster fehlt. Es gibt zwei Gründe eine Nummer zu erzwingen: # Die Nummer entspricht nicht dem bekannten Nummernschema des Ortes oder Landes. # Die Nummer liegt außerhalb der hell ausgeleuchteten Fläche. * Muss eine Nummer außerhalb der hell ausgeleuchteten Fläche platziert werden, muss zuerst die Nummer hinzugefügt und dann verschoben werden. * Wenn gespeichert wird, wirst Du aufgefordert '''Erzwingen''' anzuklicken, damit die Nummer gespeichert werden kann: [[Image:Force.png|center]] * Müssen mehrere Nummern erzwungen werden, muss nur einmal auf '''Erzwingen''' geklickt werden und alle Nummern werden gespeichert. * [[Image:Housenumbers wme_number forced.gif|right]]Wird eine Nummer durch Erzwingen gespeichert erscheint auf dem Schild mit der Nummer das Wort '''Forced'''. ==Speichern nicht vergessen!== Bevor Du '''Esc''' drückst oder auf '''Schließen''' klickst, vergiss nicht vorher zu speichern. Wenn das Speichern erfolgreich war, erscheint die Meldung:<br> [[File:SpeichernErfolgreich.png]] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 1cb90aac4f244c93fd483dd006a9e0968faa28d2 0 85 12010 2017-10-29T20:48:01Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] = Die verschiedenen Stufen = Du kannst Deine eigene [[WME Oberfläche und Steuerelemente#Ich|Stufe]…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] = Die verschiedenen Stufen = Du kannst Deine eigene [[WME Oberfläche und Steuerelemente#Ich|Stufe]] im Waze Karteneditor oben links unter deinem Benutzernamen einsehen. Die Stufen werden anhand von orangefarbenen Pilonen dargestellt.<br/>Wenn Du eine Straße im Karteneditor auswählst, kannst Du ebenso Deine Stufe einsehen, wenn Du die Straße erstellt, aufgezeichnet oder bearbeitet hast (vorher speichern). Die Stufe steht hinter dem Benutzernamen in Klammern.<br/>Beispiel: Benutzer(0) Wenn Deine Stufe tiefer ist als erwartet - basierend auf den Kriterien, die unten aufgeführt sind (Ersichtlich im [[Mein Dashboard#Your Rank and Points|Dashboard]] unter Map-Updates), melde dies im [[Glossar#DACH|DACH-Raum]] dem Selfmanagement-Team, resp. einem Manager Deines Landes (per [https://www.waze.com/forum/ucp.php?i=pm&mode=compose PM im Forum]). Selfmanagement-Team für alle DACH-Länder: *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *argus-cronos (CH) *svx-biker (CH) *pikifoo (CH) {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Level-Tabelle" |- ! Stufe / Pilonen !! Edit-Radius !! Erforderliche Mindest-Edits !! Beschreibung !! Art der Beantragung |- |class="unsortable" align="center" | 1 ||class="unsortable" align="center" | 1,6 km ||class="unsortable" align="center" | 0 || Macht sich mit dem [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] und dem [https://www.waze.com/forum/viewforum.php?f=24 Forum] vertraut. || |- |class="unsortable" align="center" | 2 ||class="unsortable" align="center" | 3,2 km ||class="unsortable" align="center" | 3.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und orientiert sich an den Regeln. Stellt (spätestens jetzt) erste Fragen im [https://www.waze.com/forum/viewforum.php?f=24 Forum], um sich weiter zu verbessern. || Hochstufung erfolgt automatisch |- |class="unsortable" align="center" | 3 ||class="unsortable" align="center" | 4,8 km ||class="unsortable" align="center" | 25.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Ist im [https://www.waze.com/forum/viewforum.php?f=24 Forum] präsent und ist per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 4 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 100.000 || Dieselben Kriterien wie Stufe 3 || PM an Self-Management-Team |- |class="unsortable" align="center" | 5 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 250.000 || Setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um. Ist im Forum aktiv und per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 6 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 500.000 || || PM an Self-Management-Team |} Unabhängig von den Edit-Stufen gibt es die Rollen ''Area Manager (AM)'' sowie ''Country Manager (CM)'': {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Rollen-Tabelle" |- ! Rolle !! Beschreibung !! Art der Beantragung |- | Area Manager (AM) || Steht in seinem AM-Gebiet den Usern unterstützend/beratend zur Seite. Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Lock-Regeln (sprich: er kann nur Segmente bis zu seinem Edit-Level bearbeiten, wie alle). Ein AM hat das Wiki gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Er ist im Forum präsent und per PM erreichbar.|| [[Der_Area_Manager|AM-Formular]] |- | Country Manager (CM) || Steht landesweit den Usern unterstützend/beratend zur Seite. Ein CM setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um und überwacht auch deren Einhaltung durch die User. Der CM arbeitet aktiv an der Weiterentwicklung der Regeln sowie deren Beschreibung mit. Er ist im Forum aktiv und per PM erreichbar. || Geeignete Kandidaten werden angesprochen |} =Rechte basierend auf Fahrten= Jeder Benutzer erhält Rechte auf den mit Waze befahrenen Straßen. Die Rechte anhand der befahrenen Straßen sind abhängig von der Stufe des Benutzers und gelten für einen vordefinierten Radius, wie in der Tabelle oben angegeben. Die Rechte, die Du während einer Fahrt erlangst, verfallen nach 3 Monaten wieder. Wenn Du ein Gebiet befahren hast, ist es daher ratsam, Änderungen oder Verbesserungen an der Karte sobald wie möglich vorzunehmen. =Rechte im Karteneditor= ==Gesperrte Segmente== Wenn ein Editor ein Segment auf eine Stufe sperrt, schützt er das Segment vor unbedachtem Bearbeiten neuer Benutzer oder Benutzer mit niedrigerer Stufe. ===Fähigkeit ein Segment zu bearbeiten=== Ein Segment kann nicht von einem Benutzer mit niedrigerer Stufe als die am Segment eingestellte Sperr-Stufe bearbeitet werden. Beispiel: Du findest ein Segment, welches auf Stufe 2 gesperrt ist. Du musst die Stufe 2 oder höher UND die Rechte im Gebiet besitzen ("Meine Gebiete" im Karteneditor), um dieses Segment bearbeiten zu können. ===Fähigkeit einen Blitzer zu bearbeiten=== Der letzte Benutzer, der einen Blitzer bearbeitet hat, sperrt diesen automatisch auf seine Stufe. Ein Benutzer mit tieferer Stufe kann den Blitzer nicht ändern oder löschen, sofern er nicht der Besitzer (Melder) ist. ==Area-Manager== [[Der Area Manager|Area-Manager]] können alles bearbeiten in ihren Gebieten, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. Eine Liste von Area-Managern gibt es [[Der_Area_Manager#AM-Liste|hier]]. ==Country-Manager== Country-Manager können alles in dem Land bearbeiten, für das sie Country-Manager sind, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. =Ein Wort der Mahnung= Beim Bearbeiten der Karte erklärst du dich damit einverstanden, die Wiki-Standards einzuhalten, die durch die Community in Deinem Land definiert wurden. Die Einhaltung der dort festgelegten Regeln und Vorschriften ist notwendig, da reale Personen im wirklichen Leben sich auf unsere Arbeit verlassen! Solltest du Fragen haben, wende dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit dir zu helfen. Ausserdem erreichst Du oft höherrangige Editoren (Level 4, 5, 6) über den Editor-Chat. Wir helfen gern und beantworten Neulingen gern immer wieder die typischen Fragen... ;-) !Beachte: Wenn du nicht nach den Richtlinien arbeitest, kannst du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn du nicht erreichbar bist und auf persönliche Nachrichten (PM) - insbesondere von Country Managern deines Landes oder Mails vom Waze-Hauptquartier - nicht antwortest, wirst du herabgestuft und deine Bearbeitungsrechte sowie deine erlangten Stufen werden dir entzogen. Dies kann sogar bis zur Sperre der Editierrechte gehen! Wir dulden keinen Vandalismus, und wir brauchen keine unbekannten Gebietsfürsten! <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] cae8996ebbfef2530921b4a4dca62ffcb3d462e5 0 86 12011 2017-10-29T20:48:54Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Geschichte des Lockings beschäftigt uns immer wieder. Sei es im Forum in allen nur erdenkbaren…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Geschichte des Lockings beschäftigt uns immer wieder. Sei es im Forum in allen nur erdenkbaren Sprachen oder hier im Wiki. Wo Du allerdings am meisten auf die Sache mit dem Locking triffst ist der Waze Map-Editor. Möchtest Du aktiv die Karten bearbeiten, dann befasse Dich ein wenig mit diesem Thema. Diese Seite bietet Dir einen Einblick in die historische Geschichte des Lockings. Lies sie sorgfälltig und verstehe sie, wenn nicht, frage uns danach im Forum. = Die Philosophie von Waze = Waze arbeitet mit einer Automatik. Dieses "Unding" verändert Straßen in ihrer Geometrie, Abbiegungen auf Kreuzungen, Fahrtrichtungen und spielt uns manchmal auch üble Streiche. Wenn Du mit Waze die Straßen befährst, werden diverse Informationen an die Server übermittelt: * Waze registriert beispielsweise, wo Du abbiegst und erlaubt in unbearbeiteten Gebieten automatisch eine Abbiegung auf der Karte. Diese Abbiegung wird dann für das Routing zugelassen. * Fahrtrichtungen werden ebenfalls registriert. Das heißt: Wenn Du nun eine Straße befährst, wird die Fahrtrichtung an Waze übermittelt und die Straße erhält eine gültige Richtung. * Straßen werden auch in ihrer Geometrie angepasst. Wenn Du mit Waze herumfährst, werden GPS-Punkte gespeichert. Mit der Zeit werden auf einer Straße immer mehr GPS-Punkte aufgezeichnet. Dies ist abhängig von der Anzahl Fahrten auf einer Straße. Waze registriert einen Mittelwert, resp. einen Punkt, wo die meisten GPS-Punkte aufeinander liegen und korrigiert den Straßenverlauf in die Mitte aller GPS-Punkte. Nun, es gibt da natürlich einen Unterschied zwischen der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] und vollständig bearbeiteten Gegenden. Dazu später mehr. = Die Vergangenheit = In der Vergangenheit oder Waze-Steinzeit galt alles oben gesagte über die Philosophie als Gesetz. Aus diesen Gründen wurde so ziemlich alles gelockt, was auch bearbeitet und als mehr oder weniger "fertig" betrachtet wurde. Einbahnstraßen behielten so ihre Richtung, die Geometrie der bereits bearbeiteten Straßen blieb so, wie sie sein sollte und die Abbiegungen der gesperrten Straßen blieben auch zu 90 % erhalten. Damals konnte der Area-Manager auch noch alles in seinem Gebiet bearbeiten. =Locking und das Rechteschema= Das [[Rechte zum Bearbeiten der Karte|Rechteschema]] wurde des öfteren angepasst. Dies einerseits, um eine gewisse Hierarchie unter den Editoren herzustellen und andererseits die wertvolle Arbeit der Editoren gegen Vandalismus zu schützen. Dies wurde so von der Community gefordert und auch nicht nur einmal.<br> Das führte so weit, dass die User per Level beschränkt wurden, um an der Karte Änderungen zu vollziehen. Also ein Level-2-Editor kann keine Straßen bearbeiten, die ein Level-3-Editor gelockt hat. Generell ging das Rechteschema immer nach Level, doch nicht in dem Ausmaß, das heute gilt. Der Area-Manager als Level-2-Editor konnte in seinem Gebiet immer alles bearbeiten, doch eine weitere Änderung im August 2012 hat dem eine Ende gesetzt. <br> Die schnell steigende Anzahl an Level-4-Editoren (damaligen Country-Managern) haben durch die Bearbeitung der Segmente, die bereits gelockt waren, alle Straßen auch auf ihren Level gelockt. Was natürlich den Area-Managern die Möglichkeit nahm, an den Segmenten Änderungen durchzuführen.<br> Die Änderungen am Rechteschema bewirkten eine regelrechte Unlock-Request-Welle in den Foren. Und man forderte, da man als AM keine Rechte an allen Straßen mehr hatte, eine Lösung. Am 13. September 2012 fand ein Massen-Unlock aller Segmente außer Freeways, Highways, Ramps und Kreisverkehren statt. Dies bescherte dem AM wieder ein wenig Luft. =Die Gegenwart= Heute ist alles anders. Die Philosophie im ersten Abschnitt und das Gesetz im zweiten Abschnitt rücken in weite Ferne. Die Probleme im dritten Abschnitt veranlassen uns zum Umdenken; unter anderem. Vieles wurde im Laufe der Zeit verändert, einiges verbessert, Server erneuert usw. Darunter fallen einige Eigenschaften, die die Philosophie heute ein wenig anders darstellen. '''Heute gilt das 11. Gebot: "Moderates Locking"''' Die Anzahl der Fahrten, die gegen Einbahnstraßen gemacht werden müssen, damit eine Richtungsänderung in einem Segment stattfindet, wurde um ein vielfaches erhöht. Die Geometrie-Anpassungen an Segmenten wurden auf aufgezeichnete Straßen beschränkt. Und generell gilt, alles was durch den Benutzer am Waze Map-Editor bearbeitet wird, behält die von ihm definierten Eigenschaften bei. In jedem Fall? - Urteile selbst! =Grundsatz der Funktion= Die "Gesperrt"-Funktion bewirkt folgendes: * Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|niedrigeren Rängen]]. * Eine Kreuzung gilt als gesperrt, wenn alle Segmente, die durch die Kreuzung verbunden sind gesperrt sind. =Die Base-Map= Wie der Titel schon sagt, handelt es sich hierbei um Basis-Karten. Ich habe im ersten Abschnitt vom Unterschied gesprochen. Wie bereits gesagt, behält alles was durch den Benutzer bearbeitet wurde seine Eigenschaften bei. Auf der rohen unbearbeiteten Base-Map kann daher die Automatik frei verfügen. Dies ist eigentlich schon alles. Die Straßen ändern ihre Richtung, wenn Wazer diese befahren und Abbiegungen werden auch automatisch gesetzt, um ein Routing zu ermöglichen. Bevor sich die Richtung einer Straße ändert, muss eine gewisse Anzahl an Fahrten in diese Richtung gemacht werden. Das heißt, der Server analysiert, wieviele Fahrten in beide Richtungen gemacht werden und entscheidet dann aufgrund einer simplen Berechnung, ob die Straße ihre Richtung ändert. Wie hoch die Anzahl ist, kann niemand genau sagen und der Support schweigt sich dazu aus, also vergiss es danach zu fragen! Schätzungen der Community im Forum gingen damals von etwa 80 Fahrten aus. Wie gesagt eine Schätzung! Da der Prozess für bearbeitete Gebiete erschwert wurde, gibt es also keinen Grund, die Straßen zu locken. Ausnahmen definieren wir - wir, die Editoren gemeinsam! Das definieren die länderspezifischen Wikis und Foren - kurzum die Community. Also informiere Dich! Die Automatik ändert auf der Base-Map auch Abbiegungen, aber sie erlaubt die Abbiegungen nur und verbietet sie nicht. Egal wie viele Fahrten Du entgegen einer Abbiegung machst, die Abbiegung bleibt erlaubt. Der angenehme Nebeneffekt ist, dass Du auch die Abbiegung in die andere Richtung zulässt. Ja, Waze ist dynamisch, dies ist die Philosophie der sich selbständig verändernden Karten. Bis zu einem gewissen Punkt, den Du auf der Karte setzen kannst! =Area-Manager und das Rechteschema= Heute fragen sich vielleicht einige, worin denn der Sinn besteht, Area-Manager zu werden, wenn er ja nicht mehr alles bearbeiten kann? Da dies bis jetzt ja immer der Vorteil dessen war. Nun, wenn Du Area-Manager bist oder sein willst, dann mach das! Die Locks der höheren Ränge: Level 4, 5 oder Country-Managern sind keinesfalls als Bevormundung anzusehen. Im Gegenteil. Du sollst Dich auch nicht darüber aufregen. Sondern mit uns allen kommunizieren, wenn etwas nicht so geht, wie Du willst. Du musst verstehen, dass der Schutz sensibler Straßen und Kreuzungen Vorrang hat, nicht jeder liest hier im Forum mit oder stöbert im Wiki nach wertvollen Informationen. Einige Benutzer basteln an der Karte herum und haben keinen Plan warum und wie. Wenn sie sich dann an Deiner harten Arbeit auslassen und "Deine" Straßen nach ihrem Geschmack ändern, spätestens dann wird Dir klar, warum dies so ist. Wird an einer Autobahn Schabernack betrieben, beeinträchtigt dies das Routing und auch Deine Navigation, teilweise für Wochen, bis neue Updates einfließen! Ein weiterer Grund, um ein wenig Qualität in die Straßen zu bringen ist: Wir Champs, Country-Manager und Level-5-Editoren haben über die geleistete Arbeit Kontrolle. Eine Kontrolle, die es dringend braucht, wie jüngst ein Beispiel aus [http://www.waze.com/forum/viewtopic.php?f=20&t=27079 Italien] zeigt. Ein Community-Projekt braucht eine gewisse Kontrolle! Finde Dich damit ab, und wenn Du irgendwo anstehst, wende Dich ans Forum und Du wirst geholfen. =Leben und leben lassen= Bedenke: Wenn Du eine Straße im Waze Map-Editor auf "Locked" setzt, sperrst Du alle Editoren aus, die einen tieferen Rang besitzen als Du selbst. Denke immer daran und setze Locks mit Bedacht an. Die Empfehlung vom Editor dieses Textes ist folgende: Wo Locks wirklich Sinn machen, dort sollst Du sie verwenden. Aber locke nicht planlos alles, nur weil Du es vor der Bearbeitung anderer Benutzer schützen willst. Die Situation auf den Straßen verändert sich ständig und die Masse macht den Teig. Andere Benutzer können sonst wichtige Änderungen, die Du vielleicht gar nicht bemerkt hast, nicht mehr anbringen. Desweiteren empfehle ich Dir, wenn Du etwas in Deiner Gegend feststellst, melde Dich per PM an die Benutzer. Bist Du Area-Manager, hast Du auch die Kontrolle über Deine Gegend und die Benutzer, die dort mitarbeiten, dies ist sogar Deine Aufgabe. Rede mit ihnen und wenn dies nicht fruchtet, wende Dich an uns im Forum. Alles klärt sich auf, früher oder später. Wie ich schon gesagt habe, wurden alle Straßen außer Freeways, Highways, Ramps und Kreisverkehre durch Waze wieder freigegeben. Beschränke Dich mit den Locks auf diese Typen. Wir Country-Manager und Level-3- oder Level-4-Editoren mit den nötigen Rechten können im Notfall immer noch eingreifen, wenn dies nötig ist. Wir sehen so auch den Stand im Gebiet, die Arbeitsweise der Editoren und können auf Probleme hinweisen resp. die Editoren unterstützen. =Die Zukunft= Der Glaskugel-Text :-) Naja, was die Zukunft wohl bringt? Das Rechteschema ist noch längst nicht im Endstadium. Man geht davon aus ein Schema zu erstellen, was sich auf die Typen der Straßen und deren Wichtigkeit im Waze-Land konzentriert. Je wichtiger die Straßen, desto beschränkter der Zugriff. Ob dies nun den Endstand darstellt, wissen wir alle nicht. Informiere Dich im Forum und lies die englischen Threads, die geben Dir sehr viele Informationen weiter. Sicher ist, ich werde immer noch da sein in der Zukunft. Viel Spaß mit Waze Gruss<br> [[User:Argus-cronos|Argus]] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 15a1e1c06d1c01c22576ed6ea9c17e83aa2f9b4a 12012 12011 2017-10-29T20:49:24Z Popel22 24 /* Die Zukunft */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Geschichte des Lockings beschäftigt uns immer wieder. Sei es im Forum in allen nur erdenkbaren Sprachen oder hier im Wiki. Wo Du allerdings am meisten auf die Sache mit dem Locking triffst ist der Waze Map-Editor. Möchtest Du aktiv die Karten bearbeiten, dann befasse Dich ein wenig mit diesem Thema. Diese Seite bietet Dir einen Einblick in die historische Geschichte des Lockings. Lies sie sorgfälltig und verstehe sie, wenn nicht, frage uns danach im Forum. = Die Philosophie von Waze = Waze arbeitet mit einer Automatik. Dieses "Unding" verändert Straßen in ihrer Geometrie, Abbiegungen auf Kreuzungen, Fahrtrichtungen und spielt uns manchmal auch üble Streiche. Wenn Du mit Waze die Straßen befährst, werden diverse Informationen an die Server übermittelt: * Waze registriert beispielsweise, wo Du abbiegst und erlaubt in unbearbeiteten Gebieten automatisch eine Abbiegung auf der Karte. Diese Abbiegung wird dann für das Routing zugelassen. * Fahrtrichtungen werden ebenfalls registriert. Das heißt: Wenn Du nun eine Straße befährst, wird die Fahrtrichtung an Waze übermittelt und die Straße erhält eine gültige Richtung. * Straßen werden auch in ihrer Geometrie angepasst. Wenn Du mit Waze herumfährst, werden GPS-Punkte gespeichert. Mit der Zeit werden auf einer Straße immer mehr GPS-Punkte aufgezeichnet. Dies ist abhängig von der Anzahl Fahrten auf einer Straße. Waze registriert einen Mittelwert, resp. einen Punkt, wo die meisten GPS-Punkte aufeinander liegen und korrigiert den Straßenverlauf in die Mitte aller GPS-Punkte. Nun, es gibt da natürlich einen Unterschied zwischen der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] und vollständig bearbeiteten Gegenden. Dazu später mehr. = Die Vergangenheit = In der Vergangenheit oder Waze-Steinzeit galt alles oben gesagte über die Philosophie als Gesetz. Aus diesen Gründen wurde so ziemlich alles gelockt, was auch bearbeitet und als mehr oder weniger "fertig" betrachtet wurde. Einbahnstraßen behielten so ihre Richtung, die Geometrie der bereits bearbeiteten Straßen blieb so, wie sie sein sollte und die Abbiegungen der gesperrten Straßen blieben auch zu 90 % erhalten. Damals konnte der Area-Manager auch noch alles in seinem Gebiet bearbeiten. =Locking und das Rechteschema= Das [[Rechte zum Bearbeiten der Karte|Rechteschema]] wurde des öfteren angepasst. Dies einerseits, um eine gewisse Hierarchie unter den Editoren herzustellen und andererseits die wertvolle Arbeit der Editoren gegen Vandalismus zu schützen. Dies wurde so von der Community gefordert und auch nicht nur einmal.<br> Das führte so weit, dass die User per Level beschränkt wurden, um an der Karte Änderungen zu vollziehen. Also ein Level-2-Editor kann keine Straßen bearbeiten, die ein Level-3-Editor gelockt hat. Generell ging das Rechteschema immer nach Level, doch nicht in dem Ausmaß, das heute gilt. Der Area-Manager als Level-2-Editor konnte in seinem Gebiet immer alles bearbeiten, doch eine weitere Änderung im August 2012 hat dem eine Ende gesetzt. <br> Die schnell steigende Anzahl an Level-4-Editoren (damaligen Country-Managern) haben durch die Bearbeitung der Segmente, die bereits gelockt waren, alle Straßen auch auf ihren Level gelockt. Was natürlich den Area-Managern die Möglichkeit nahm, an den Segmenten Änderungen durchzuführen.<br> Die Änderungen am Rechteschema bewirkten eine regelrechte Unlock-Request-Welle in den Foren. Und man forderte, da man als AM keine Rechte an allen Straßen mehr hatte, eine Lösung. Am 13. September 2012 fand ein Massen-Unlock aller Segmente außer Freeways, Highways, Ramps und Kreisverkehren statt. Dies bescherte dem AM wieder ein wenig Luft. =Die Gegenwart= Heute ist alles anders. Die Philosophie im ersten Abschnitt und das Gesetz im zweiten Abschnitt rücken in weite Ferne. Die Probleme im dritten Abschnitt veranlassen uns zum Umdenken; unter anderem. Vieles wurde im Laufe der Zeit verändert, einiges verbessert, Server erneuert usw. Darunter fallen einige Eigenschaften, die die Philosophie heute ein wenig anders darstellen. '''Heute gilt das 11. Gebot: "Moderates Locking"''' Die Anzahl der Fahrten, die gegen Einbahnstraßen gemacht werden müssen, damit eine Richtungsänderung in einem Segment stattfindet, wurde um ein vielfaches erhöht. Die Geometrie-Anpassungen an Segmenten wurden auf aufgezeichnete Straßen beschränkt. Und generell gilt, alles was durch den Benutzer am Waze Map-Editor bearbeitet wird, behält die von ihm definierten Eigenschaften bei. In jedem Fall? - Urteile selbst! =Grundsatz der Funktion= Die "Gesperrt"-Funktion bewirkt folgendes: * Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|niedrigeren Rängen]]. * Eine Kreuzung gilt als gesperrt, wenn alle Segmente, die durch die Kreuzung verbunden sind gesperrt sind. =Die Base-Map= Wie der Titel schon sagt, handelt es sich hierbei um Basis-Karten. Ich habe im ersten Abschnitt vom Unterschied gesprochen. Wie bereits gesagt, behält alles was durch den Benutzer bearbeitet wurde seine Eigenschaften bei. Auf der rohen unbearbeiteten Base-Map kann daher die Automatik frei verfügen. Dies ist eigentlich schon alles. Die Straßen ändern ihre Richtung, wenn Wazer diese befahren und Abbiegungen werden auch automatisch gesetzt, um ein Routing zu ermöglichen. Bevor sich die Richtung einer Straße ändert, muss eine gewisse Anzahl an Fahrten in diese Richtung gemacht werden. Das heißt, der Server analysiert, wieviele Fahrten in beide Richtungen gemacht werden und entscheidet dann aufgrund einer simplen Berechnung, ob die Straße ihre Richtung ändert. Wie hoch die Anzahl ist, kann niemand genau sagen und der Support schweigt sich dazu aus, also vergiss es danach zu fragen! Schätzungen der Community im Forum gingen damals von etwa 80 Fahrten aus. Wie gesagt eine Schätzung! Da der Prozess für bearbeitete Gebiete erschwert wurde, gibt es also keinen Grund, die Straßen zu locken. Ausnahmen definieren wir - wir, die Editoren gemeinsam! Das definieren die länderspezifischen Wikis und Foren - kurzum die Community. Also informiere Dich! Die Automatik ändert auf der Base-Map auch Abbiegungen, aber sie erlaubt die Abbiegungen nur und verbietet sie nicht. Egal wie viele Fahrten Du entgegen einer Abbiegung machst, die Abbiegung bleibt erlaubt. Der angenehme Nebeneffekt ist, dass Du auch die Abbiegung in die andere Richtung zulässt. Ja, Waze ist dynamisch, dies ist die Philosophie der sich selbständig verändernden Karten. Bis zu einem gewissen Punkt, den Du auf der Karte setzen kannst! =Area-Manager und das Rechteschema= Heute fragen sich vielleicht einige, worin denn der Sinn besteht, Area-Manager zu werden, wenn er ja nicht mehr alles bearbeiten kann? Da dies bis jetzt ja immer der Vorteil dessen war. Nun, wenn Du Area-Manager bist oder sein willst, dann mach das! Die Locks der höheren Ränge: Level 4, 5 oder Country-Managern sind keinesfalls als Bevormundung anzusehen. Im Gegenteil. Du sollst Dich auch nicht darüber aufregen. Sondern mit uns allen kommunizieren, wenn etwas nicht so geht, wie Du willst. Du musst verstehen, dass der Schutz sensibler Straßen und Kreuzungen Vorrang hat, nicht jeder liest hier im Forum mit oder stöbert im Wiki nach wertvollen Informationen. Einige Benutzer basteln an der Karte herum und haben keinen Plan warum und wie. Wenn sie sich dann an Deiner harten Arbeit auslassen und "Deine" Straßen nach ihrem Geschmack ändern, spätestens dann wird Dir klar, warum dies so ist. Wird an einer Autobahn Schabernack betrieben, beeinträchtigt dies das Routing und auch Deine Navigation, teilweise für Wochen, bis neue Updates einfließen! Ein weiterer Grund, um ein wenig Qualität in die Straßen zu bringen ist: Wir Champs, Country-Manager und Level-5-Editoren haben über die geleistete Arbeit Kontrolle. Eine Kontrolle, die es dringend braucht, wie jüngst ein Beispiel aus [http://www.waze.com/forum/viewtopic.php?f=20&t=27079 Italien] zeigt. Ein Community-Projekt braucht eine gewisse Kontrolle! Finde Dich damit ab, und wenn Du irgendwo anstehst, wende Dich ans Forum und Du wirst geholfen. =Leben und leben lassen= Bedenke: Wenn Du eine Straße im Waze Map-Editor auf "Locked" setzt, sperrst Du alle Editoren aus, die einen tieferen Rang besitzen als Du selbst. Denke immer daran und setze Locks mit Bedacht an. Die Empfehlung vom Editor dieses Textes ist folgende: Wo Locks wirklich Sinn machen, dort sollst Du sie verwenden. Aber locke nicht planlos alles, nur weil Du es vor der Bearbeitung anderer Benutzer schützen willst. Die Situation auf den Straßen verändert sich ständig und die Masse macht den Teig. Andere Benutzer können sonst wichtige Änderungen, die Du vielleicht gar nicht bemerkt hast, nicht mehr anbringen. Desweiteren empfehle ich Dir, wenn Du etwas in Deiner Gegend feststellst, melde Dich per PM an die Benutzer. Bist Du Area-Manager, hast Du auch die Kontrolle über Deine Gegend und die Benutzer, die dort mitarbeiten, dies ist sogar Deine Aufgabe. Rede mit ihnen und wenn dies nicht fruchtet, wende Dich an uns im Forum. Alles klärt sich auf, früher oder später. Wie ich schon gesagt habe, wurden alle Straßen außer Freeways, Highways, Ramps und Kreisverkehre durch Waze wieder freigegeben. Beschränke Dich mit den Locks auf diese Typen. Wir Country-Manager und Level-3- oder Level-4-Editoren mit den nötigen Rechten können im Notfall immer noch eingreifen, wenn dies nötig ist. Wir sehen so auch den Stand im Gebiet, die Arbeitsweise der Editoren und können auf Probleme hinweisen resp. die Editoren unterstützen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 61bf29e975ad805e4ce89ad1f84d58a9f0e68726 0 87 12013 2017-10-29T20:49:55Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Übersicht= Wenn mit Waze navigiert wird, kontrolliert das Routing den Fahrweg anhand des Wie_Wa…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Übersicht= Wenn mit Waze navigiert wird, kontrolliert das Routing den Fahrweg anhand des [[Wie_Waze_Routen_kalkuliert#Penalty-System | Penalty-Systems]]. Das heisst: Weniger bevorzugte Straßen oder Abbiegungen besitzen einen höheren Penalty bei der Berechnung einer Route von A nach B. Je höher die berechneten Penalties sind, desto weniger wird Waze durch diese Segmente und Abbiegungen routen. Daher wird die Route mit den tiefsten Penalties, kombiniert mit Distanzen und Verkehrsinformationen gewählt. Eine Kreuzung entsteht wenn ein Segment mit einem anderen verbunden wird. An einer Kreuzung besteht die Möglichkeit zu kontrollieren, wie Waze durch diese Kreuzung zwischen den Segmenten navigiert. Dies wird durch rote und grüne Pfeile im Waze Map-Editor gesteuert abhängig davon, ob die Durchfahrt an der Kreuzung erlaubt ist oder nicht. Diese Einstellungen nennen wir Abbiegungen oder Abbiegeverbote. Bevor Du hier weiter liest, mach Dich mit dem Thema [[Erstellen_und_bearbeiten_eines_Segments#Abbiegungen_bearbeiten | Abbiegungen bearbeiten]] vertraut. ==Wichtige Begriffe== '''Abbiegung verboten''' - [[Image:Arrow_Red-2.png‎]][[Image:Arrow_Red-2-question2.png]] - Wird mit einem roten Pfeil dargestellt und erzeugt einen hohen Penalty für das Routing, von einem Segment zum anderen durch diese Kreuzung. '''Abbiegung erlaubt''' - [[Image:Arrow_Green-2.png]][[Image:Arrow_Green-2-question2.png]] - Wird mit einem grünen Pfeil dargestellt und erzeugt einen tieferen Penalty für das Routing, von einem Segment zum anderen durch diese Kreuzung. '''Soft Turn''' - [[Image:Arrow_Red-2-question2.png]][[Image:Arrow_Green-2-question2.png]] - Der Waze Map-Editor zeigt "Soft Turns" mit einem violetten Fragezeichen an. Sie werden automatisch durch das Waze-Routingmodul generiert, wenn Abbiegungen von bestehenden Segmenten zu bestehenden oder neuen Kreuzungen hinzugefügt werden. Bestehende Segmente haben Hard Restricted Turns an der Kreuzung, wenn neue Segmente hinzugefügt werden. Unbearbeitete Kreuzungen auf der Base-Map haben Soft Restricted Turns. '''Hard Turn''' - [[Image:Arrow_Red-2.png‎]][[Image:Arrow_Green-2.png]] - Der Waze Map-Editor unterscheidet zwischen '''Hard''' und '''Soft''' Turns, wenn auf das Fragezeichen geklickt wird und die Abbiegung manuell von einem Editor erlaubt oder verboten wird. Es gibt vier Status, welche in der Tabelle hier erklärt werden: {| class="wikitable unsortable" border="1" |+ Soft und Hard Turn Kombinationen |- ! Pfeil ! Status ! Penalty ! Wird erzeugt durch ! Informationen |- style="background:#FA5858; color:black" | bgcolor="white"|[[Image:Arrow_Red-2.png‎]] | Hard Restricted | Sehr hoch | Wenn ein Editor auf den Pfeil klickt und von grün auf rot wechselt oder von rot nach grün und wieder nach rot | Waze routet generell nicht durch diese Abbiegung |- style="background:#F5A9A9; color:black" | bgcolor="white"|[[Image:Arrow_Red-2-question2.png]] | Soft Restricted | Hoch | Neu erstellte Abbiegungen, wenn bestehende Segmente miteinander verbunden werden<br> Ausgehend von bestehenden Segmenten, wenn mit neuen Segmenten verbunden wird | Dieser Status kann nicht manuell durch Anklicken der Pfeile erzeugt werden |- style="background:#A9F5A9; color:black" | bgcolor="white"|[[Image:Arrow_Green-2-question2.png]] | Soft Enabled | Tief | Automatisch generierte Abbiegungen durch Waze, wenn genug Fahrten durch den '''Soft''' Restricted Turn registriert wurden | Waze ändert keinen '''Hard''' Restricted Turn durch das Befahren in der Gegenrichtung |- style="background:#58FA58; color:black" | bgcolor="white"|[[Image:Arrow_Green-2.png]] | Hard Enabled | Sehr tief | Wenn ein Editor auf den Pfeil klickt und von rot nach grün wechselt oder von grün nach rot und wieder zu grün | Wird auch erzeugt wenn die Kreuzung ausgewählt wird und die Tastaturkürzel '''Q''' und dann '''W''' gedrückt werden |- |} <br> ==Tastaturkürzel== [[Image:Abbiegungen erlauben.png|left]] Auf der linken Seite siehst Du das Eigenschaftsfenster. Es wird angezeigt, wenn eine Kreuzung ausgewählt wird. Ja nach Status der Kreuzung wird '''Alle Abbiegungen erlauben''' oder '''Alle Abbiegungen verbieten''' angezeigt. Beispiel: Wenn alle Abbiegungen erlaubt sind wird nur '''Alle Abbiegungen verbieten''' angezeigt und die Information, dass alle Abbiegungen erlaubt sind. Im Gegensatz zum Bild links. <br clear="all" /> Du kannst auch die Tastaturkürzel '''W''' "Alle Abbiegungen erlauben" oder '''Q''' "Alle Abbiegungen verbieten" verwenden. Weitere hilfreiche Tastaturkürzel: * '''Shift+z''' wechselt zwischen: 1) Zeigt die Verbotenen oder erlaubten Abbiegungen an für ein ausgewähltes Segment, und 2) Zeigt alle Verbotenen Abbiegungen im gewählten Kartenausschnitt an (bis zur Zoom-Stufe 4 oder 100 m), wenn kein Segment ausgewählt ist. * '''a''' macht die Pfeile transparent. Hilfreich, wenn die Pfeile etwas überdecken, das bearbeitet werden soll. Ist ein Pfeil transparent, kann er nicht angeklickt werden. * '''s''' spreizt die Pfeile auseinander. Dies ist Hilfreich, wenn mehrere Pfeile übereinander liegen. Um alle Tastaturkürzel anzuzeigen drücke '''?''' oder klicke auf den Link unten links im Karteneditor. [[File:EditorLinks.png]] ==Beste Vorgehensweise== Wenn eine neue Kreuzung hinzugefügt wurde, vergewissere Dich, dass alle Fahrrichtungen der verbundenen Segmente korrekt sind. Dann sollten alle Abbiegungen mit '''Q''' verboten und wieder mit '''W''' erlaubt werden. Danach müssen alle verbotenen Abbiegungen einzeln gesetzt werden. Wenn ein Segment von einer Kreuzung abgetrennt wird und und wieder mit der Kreuzung oder einer anderen verbunden wird, werden die Abbiegungen vom betreffenden Segment her wieder '''Soft''' Turns. Um die Abbiegungen wieder '''Hard''' zu machen, folge der besten Vorgehensweise, die oben beschrieben ist. ==Routen Berechnung== Mehr Informationen finden sich hier: [[Wie Waze Routen kalkuliert]]. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 66b2a7294792f4ce5fb94f0af030aeeac691c6c5 0 88 12014 2017-10-29T20:50:26Z Popel22 24 Die Seite wurde neu angelegt: «<!--Editorial Reminders--> <!--To Do - Bow Tie intersections --> <!--To Do - U-Turn Solutions for "Road not connected" error --> <!--Limited Acces Interchange Pu…» wikitext text/x-wiki <!--Editorial Reminders--> <!--To Do - Bow Tie intersections --> <!--To Do - U-Turn Solutions for "Road not connected" error --> <!--Limited Acces Interchange Punkt 7 --> <!--Fake-Nodes 8.2.2 --> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Diese Seite beinhaltet wichtige Informationen über das Erstellen von Kreuzungen und den Straßen dazwischen. Lies diese Seite durch, bevor Du an der Karte arbeitest. == Einfacher ist besser == Bei der Darstellung von Kreuzungen müssen wir manchmal die Realität, den Möglichkeiten von Waze anpassen. Das Hauptziel sollte dabei sein, die Dinge so einfach wie möglich darzustellen und Komplexe Kreuzungen nur da zu verwenden, wo sie unbedingt nötig sind. Schau Dir dazu auch die Seite [[Base Map 1.0]] an. == Grundsatz == === Was ist eine Straßenkreuzung? === Eine Straßenkreuzung besteht aus drei Dingen: # Mindestens zwei Straßen # Einer oder mehrere Punkte, durch die sich diese Straßen kreuzen (Kreuzung) # Erlaubte oder verbotene Abbiegungen Wenn Du nicht weißt, wie man Straßen, Kreuzungen und Abbiegungen bearbeitet, dann lies hier die [[WME_Schnellstart-Anleitung|WME Schnellstart-Anleitung]]. === Einfache Kreuzung === Beginnen wir mit einer einfachen Kreuzung. Der Abzweiger trifft normalerweise in einem 90-Grad-Winkel auf die "Hauptstraße". Dies ist die einfachste Situation auf der Karte. : [[Image:Jct_3_90_ex.png]] [[Image:Jct_3_90.png]] Du wirst auf Straßen antreffen, die in ungewöhnlichen Winkeln aufeinander treffen. Auch in städtischen Gebieten mit starren Gittern, kreuzen sich Straßen in verschiedensten Winkeln. Der erste Gedanke hier wird wahrscheinlich sein, die Kreuzungen auch so darzustellen, wie sie offensichtlich existieren - zwei Linien, die aufeinander treffen in einem spitzen Winkel. : [[Image:Jct_3_45_ex1.png]] [[Image:Jct_3_45.png]] Aber an solchen Kreuzungen entstehen Probleme. Abhängig vom Winkel sagt Waze evtl. ein '''"Rechts halten"''' an, wo ein '''"Rechts abbiegen"''' erwartet wird. Wenn '''"Minor Highways"'''(Landesstraßen) oder höhere Straßentypen verwendet werden, gar ein '''"Ausfahrt rechts"''', was für den Fahrer in manchen Situationen verwirrend klingt. In einigen Fällen gibt Waze gar keine Navigationsanweisungen. Im schlechtesten Fall nimmt das Routing an, dass eine solche Abbiegung gar nicht möglich ist (Im Beispiel oben, von Norden kommend und nach links abbiegen Richtung Osten) und schlägt diese schon gar nicht vor, während der Navigation. Auch entstehen automatische Kartenfehler, wegen Abbiegungen, die zu weit von der Kreuzung entfernt liegen. Um diese Kreuzungen korrekt zu erstellen, und ein '''"Rechts abbiegen"''' oder '''"Links abbiegen"''' zu erhalten von TTS, müssen wir sie so darstellen, dass wieder ein 90-Grad-Winkel entsteht. Dies erreichen wir, indem wir zusätzliche Geometrie-Punkte hinzufügen und eine Kurve bei einer der Straßen zeichnen. : [[Image:Jct_3_45_curve.png]] Nun haben wir wieder eine Kreuzung, die wie eine normale 90-Grad-Straßenkreuzung funktioniert. Die Navigationsanweisungen sind korrekt und die automatischen Kartenfehler entstehen auch nicht: : [[Image:Jct_3_45_ex.png|200px]] === Kreuzungen mit Ramp Segmenten=== Ein- und Ausfahrten (Ramps) an Autobahnen, sind ein anderes gutes Beispiel, wo zusätzliche Geometrie-Punkte sehr hilfreich sind. Speziell, da die meisten Ein- und Ausfahrten in einem sehr kleinen Winkel abzweigen. : [[Image:Jct_ramp_no_geo_ex.png]] [[Image:Jct_ramp_no_geo.png]] Der Nachteil in all diesen Fällen (den gibt es auch für das Beispiel oben) ist, man sieht die Abbiegungen nicht und es erschwert das korrekte setzen der Abbiegungen im Waze Map-Editor. : [[Image:Jct_ramp_no_geo_arrow.png]] Aber wenn wir nur einen Geometrie-Punkt hinzufügen und den Anfangswinkel näher an 20-30 Grad bringen... (Wieso diese Winkel? Schau Dir die [[#Geometrie|Informationen über Geometrie und Abbiegeanweisungen]] weiter unten auf dieser Seite an)... : [[Image:Jct_ramp_w_geo_ex.png]] [[Image:Jct_ramp_w_geo.png]] ...jetzt sind die Pfeile sichtbar und können bearbeitet werden. Mit der '''s'''-Taste kannst Du die Pfeile auseinander splitten, damit sie besser bearbeitet werden können. Informationen zu den Tastaturkürzeln findest Du [[WME_Schnellstart-Anleitung#Tastaturk.C3.BCrzel|hier]]. : [[Image:Jct_ramp_w_geo_arrow.png]] Mit dem haben wir nun sicher gestellt, daß die Kreuzung so funktioniert, wie sie sollte. Wir haben der Ramp einen anderen Winkel hinzugefügt und können die Abbiegungen mit Leichtigkeit bearbeiten. === Kreuzung mit vier Fahrtrichtungen === Wir können die obigen Ansätze bei einer "Vier-Wege-Kreuzung" anwenden. Und wieder können wir auch 90-Grad-Winkel erwarten. : [[Image:Jct_4_90_ex.png]] [[Image:Jct_4_90.png‎ ]] Haben wir eine "Vier-Wege-Kreuzung" mit spitzen Winkeln, müssen wir diese ändern. : [[Image:Jct_4_45_ex1.png]] [[Image:Jct_4_45.png]] Wir arbeiten wieder mit einem Geometrie-Punkt an zwei Straßen, um den Winkel an die besagten 90 Grad heranzuführen. Vergrößere die Ansicht (Zoom-Stufe) im Waze Map-Editor, so kannst Du die Winkel praktisch unsichtbar machen für die Benutzer der Waze-App. : [[Image:Jct_4_45_curve.png]] Das Bild hier oben siehst Du, wenn Du die Ansicht im Waze Map-Editor auf die größtmöglichste Stufe vergrößerst. Verkleinerst Du die Ansicht wieder nach der Bearbeitung, wird die Kreuzung fast so aussehen wie zuvor. Hier ist ein reales Beispiel. Du kannst bei dieser Zoom-Stufe immer noch die Geometrie-Punkte sehen: : [[Image:Jct_4_45_ex.png]] Mit dieser Anpassung erhalten wir korrekte Navigationsanweisungen, wie '''"Rechts abbiegen"''' oder '''"Links abbiegen"'''. == Kontrollieren der Abbiegeanweisungen == Bevor Du nun weitermachst, solltest Du das Thema [[WME_Schnellstart-Anleitung#Abbiegungen|Abbiegungen]] gelesen und verstanden haben. Wenn die Abbiegungen nicht korrekt gesetzt werden, wird es auch nie korrekte Abbiegeanweisungen geben! Verstehe auch den Unterschied zwischen [[Soft und Hard Turns|Soft- und Hard-Turns]]. Im [[#Grundsatz|Grundsatz-Abschnitt]] oben, haben wir gelernt, wie man "Links-/Rechtsabbiegen" gegenüber "Links-/Rechtshalten" priorisieren kann, damit korrekte Abbiegeanweisungen erfolgen. Informationen dazu enthält diese Seite: [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|How Waze determines turn / keep / exit maneuvers]], aber eine Zusammenfassung findet sich im nächsten Abschnitt. === Geometrie === Wenn Du bei der Bearbeitung der Kreuzungen ein paar Grundregeln befolgst, ist es viel einfacher das Navigationsverhalten einer Kreuzung vorherzusagen, ohne dass Du dich mit den Details des Hintergrund-Algorithmus befassen musst. {|class="wikitable" border="1" style="text-align:center;" |- ! style="background: #99FF99;" | Abbiegewinkel ! style="background: #99FF99;" scope="col" width="75px" | Spanne ! style="background: #99FF99;" | Straßentyp ! style="background: #99FF99;" scope="col" width="225px" | Ansage |- | Rowspan="3" | 22° | Rowspan="3" | 0°-44° | Alle außer Rampe, Bundes-/Landesstraße, Autobahn | Links '''halten''' und Rechts '''halten''' |- | Rowspan="2" | Rampe, Bundes-/Landesstraße, Autobahn |- | Links '''halten''' und '''Ausfahrt''' rechts nehmen |- | 90° | 45° - 150° | Alle | Links '''abbiegen''' und Rechts'''abbiegen''' |} Links sieht man den empfohlenen Winkel. Wie man sieht, erzeugt eine breite Spanne von Werten die gleiche Ansage. Die empfohlenen Werte sind mit bloßem Auge leicht zu unterscheiden. Wichtig: Winkel um 45° sollten vermieden werden. Bereits ein halbes Grad Ungenauigkeit kann hier zur nicht gewünschten Ansage führen. Auch Scripte wie "Junction Angle Info" sind nicht zuverlässig genug um zuverlässig zwischen 44° und 45° zu unterscheiden. Weiter sollten Winkel unter 10° vermieden werden. Im WME sind dann die Pfeile schwer anwählbar, und in der App kann man bei Sperrungen das Segment schlecht antippen. Wenn wir eine [[#Y-Verzweigung|Y-Verzweigung]] bearbeiten, und wir wollen darüber im Klaren sein, welcher Zweig "gerade aus" führt und welcher abzweigt, ist dies bei einem Winkel für "Zweig 1" mit 0 Grad und "Zweig 2" mit 5 Grad nicht so klar. Aber "gerade aus" ist viel klarer, wenn die Winkel für "Zweig 1" bei 0 Grad und "Zweig 2" bei 20 Grad liegen. Da die meisten von uns nicht mit Winkelmessern arbeiten, ist es am besten, Situationen zu vermeiden, wo diese Genauigkeit eine Rolle spielt. Dieses Wissen ermöglicht es uns, zu kontrollieren, wie sich eine Kreuzung durch Verändern eines einzigen Geometrie-Punkts, in den meisten Fällen verhält. Dies ist vor allem bei Abbiegespuren wichtig, wo wir manchmal ein '''"Rechts-/Links halten"''' bevorzugen und manchmal ein '''"Rechts-/Links abbiegen"''' wiederum besser erscheint. Wenn wir den Anfangswinkel zwischen 20 und 30 Grad halten, können wir hier ein '''"Rechts halten"''' erwarten auf der Abbiegespur: : [[Image:Jct_at_grade_keep.png]] Wenn wir aber den Geometrie-Punkt zu einem 90-Grad-Winkel verschieben, würden wir hier ein '''"Rechts abbiegen"''' erhalten. : [[Image:Jct_at_grade_turn.png]] Das Gleiche gilt für das Ende der Abbiegespur. Wenn der Winkel am Ende des Segments zwischen 20 und 30 Grad liegt folgt keine Abbiegeanweisung. Wenn der Winkel jedoch am Ende 90 Grad beträgt, wäre die Anweisung '''"Rechts abbiegen"''', was nicht sehr sinnvoll wäre. Wäre die Nord-Süd Straße im letzten Beispiel ein Major- oder Minor Highway (Bundes- oder Landesstraße), würde die 20 bis 30-Grad-Regel am Anfang der Abbiegespur eine '''"Ausfahrt rechts"''' Anweisung produzieren. Dies wäre noch verwirrender als '''"Rechts halten"'''. Daher sollte auch wenn die Abbiegespur ein Ausfahrtsschild besitzt, ein 90-Grad-Winkel, der ein '''"Rechts abbiegen"''' produziert bevorzugt werden. === Benennung und Klassifizierung der Segmente === Die Namen und Straßentypen beeinträchtigen das Routing zusätzlich zur Geometrie der Segmente. Ein Faustregel ist: Willst Du eine Navigationsanweisung, wird eine unterschiedliche Benennung die Chancen erhöhen(Keine Garantie). Im Fall der Abbiegespur oben, sollte dieses Segment einen anderen Namen tragen, als das Segment von dem sie wegführt, oder gar nicht benannt werden (Lies dazu [[Abbiegespuren#Benennung |Benennung]] auf der Seite Abbiegespuren). Der Straßentyp ist ein Faktor in der Navigation, doch die Namen und die Winkel sind viel wichtiger. Wenn mehrere Straßen auf eine Kreuzung treffen und zwei davon verbinden sich bei nahezu 0 Grad, haben den selben Namen, dann wird dies immer als "gerade aus" angesehen, egal welche Straßentypen verwendet werden. Ein Beispiel dazu gibt es später hier: [[#Y-Verzweigung|Y-Verzweigung]]. Straßentypen sind ein entscheidender Faktor, wenn alle unterschiedlich benannt sind Ein Beispiel: Stell Dir eine Ramp vor, welche auf einen Freeway und eine andere Ramp führt. Die Ramp wird als weiterführendes Segment gesehen, daher wird es keine Navigationsanweisung geben, wenn man bei der Kreuzung auf die nächste Ramp fährt. Wechselt man aber von der Ramp auf den Freeway, wird eine Anweisung angesagt. Das sogar, wenn die Ramp und der Freeway sich bei einem Winkel von 0 Grad treffen und die weiterführende Ramp abzweigt bei einem Winkel von 20 bis 30 Grad. ===Segmente in Kreuzungen=== =====Benennung===== Bei Straßensegmenten die innerhalb einer Kreuzung verlaufen, bleibt der Straßenname leer. Das Benennen dieser Felder führt zu falschen Ansagen für Abbieger. Das Segment darf nur benannt werden, wenn eine falsche Ansage für alle Abbiegerichtungen ausgeschlossen werden kann, auch für erlaubte U-Turns. Im Zweifel ist das Segment nicht zu benennen. Im Bild haben die Hauptstraßen-Segmente unterschiedliche Namen, daher bleibt das ausgewählte Segment in der Mitte namenlos. [[Image:Hannover.png|700px]] =====Minimallänge===== Wenn an solch einem Segment ein U-Turn (180°-Wende) erlaubt sein soll, dann muss das Segment mindestens 15m lang sein. Unter 15m kann man davon ausgehen, dass der Routingserver keinen U-Turn vorsieht. Dabei ist zu beachten, dass die Segmentlänge im Editor immer gerundet ist. Im Zweifelsfall sind 16m zuverläsiger als 15m. Eine zuverlässige Alternative zum H-förmig gezeichneten U-Turn ist der Bow-Tie, der volle Kontrolle über das Erlauben oder Verbieten von U-turns bietet. [[Kreuzungen#Bow_tie_Kreuzung|-> Bow-Tie]] === U-Turns === U-Turns werden nur an den Kreuzungen auf grün gestellt, wo das Wenden in einem Zug ohne Eigen- oder Fremd-Gefährdung möglich ist. Bei den allermeisten Kreuzungen ist der U-Turn-Pfeil daher rot zu stellen bzw. zu belassen. == Asphaltierte Straßen == === Y-Verzweigung === Wenn Y-Verzweigungen erstellt werden, muss sehr genau darauf geachtet werden, wie sie erstellt werden, um korrekte Anweisungen zu erhalten. Die Namen der Segmente und die Geometrie sind sehr wichtig. (S. auch [[How_Waze_determines_turn_/_keep_/_exit_maneuvers|How Waze Determines turn/keep/exit maneuvers]]) Im Beispiel unten ist die mehrspurige Straße bekannt als Main Street nach Westen und als Atlantic Avenue nach Osten. Die Namensänderung geschieht ab der Kreuzung wo die Main Street abzweigt. : [[Image:Jct_Y_ex_aerial.png|200px]] Die Beschreibung oben ist in etwa so, wie wir die Situation sehen. Aber wie aus dem Bild hervorgeht, wäre die technische Beschreibung eher, daß die Main Street in einer geraden Verbindung weiterführt und die Atlantic Avenue abzweigt. Doch wenn wir sie so darstellen auf der Karte, produzieren wir damit ein Problem. : [[Image:Jct_Y_ex_map_bad.png|200px]] Da die zwei Segmente der Main Street beide den selben Namen haben, geht der Routing-Server davon aus, daß diese Verbindung "geradeaus" führt, so wie wir sie aus der Luft hier auch sehen. Wenn die zwei Segmente nun eine Gerade bilden verstärken wir damit die Annahme, daß von Main Street nach Main Street "geradeaus" sein muss. Doch geradeaus ist in unserem Fall von der Main Street nach Atlantic Avenue. Also weiter auf der mehrspurigen Straße ungeachtet der Namensänderung. Damit der Routing-Server nun die Situation auch versteht, müssen wir die Geometrie der Segmente anpassen. Das Resultat zeigt sich im nächsten Bild: : [[File:Jct Y ex map.png|200px]] Auf der mehrspurigen Straße haben wir den Übergang bei der Kreuzung, auf einem Winkel von nahezu 0 Grad gesetzt. Die Main Street(Street-Segment) zweigt in einem Winkel von 90 Grad ab. Der Routing-Server sollte jetzt auch wissen, daß hier eine Abbiegung vorhanden ist. Das Resultat ist, daß nun eine Abbiegeanweisung angesagt wird, nämlich von Main Street(Primary-Segment) nach Main Street(Street-Segment) genau so, wie es der Fahrer auf der Straße erwarten würde. === Nicht durchgängig befahrbare Straßen === Straßen die nur über einen Weg hinein und über den gleichen wieder hinaus führen, können eine ziemliche Herausforderung sein für den Routing-Server, obwohl dies für uns sehr einfach zu sein scheint. ==== Sackgassen ==== Sackgassen sind im Waze Map-Editor simple Segmente, ohne Verbindung auf andere Segmente am Ende. Die Klassifizierung und Benennung richtet sich nach den länderspezifischen Wikis, der tatsächlichen Situation und den offiziellen Namen. <br> '''Am Ende jeder Sackgasse befindet sich eine Kreuzung''' ([[Glossar|End-Node]]). : [[Image:Jct_dead_end.png|200px]] Die Kreuzung am Ende muss sich auch innerhalb der befahrbaren Sackgasse befinden. Waze kann die Straße nur bestätigen, wenn beide Kreuzungen auch befahren werden können. Wenn sich die Kreuzung ausserhalb der befahrbahren Fläche befindet, ist es unmöglich diese zu erreichen. Daher sollte die Sackgasse nicht bis ganz ans Ende gezogen werden, auch besteht die Möglichkeit, dass die Aerials nicht korrekt sind. : [[Image:Jct_dead_end_ex.png|200px]] Wie im Bild zu sehen, hat hier der Fahrer die Möglichkeit, das Ende auch zu erreichen. ==== Cul-de-sacs ==== ''Infos gibt es hier: [http://en.wikipedia.org/wiki/Cul-de-sac Cul-de-sac bei Wikipedia]'' Cul-de-sac (In den USA auch Court genannt) trifft man oft an, als Sackgasse in Wohngebieten. Sie hat hat einen Kreis oder eine Schlaufe am Ende. In den meisten Fällen sollte man diese wie eine normale Sackgasse mappen, mit einer Kreuzung am Ende. : [[Image:Jct_cul-de-sac_ex.png|200px]] Das Ende der Straße sollte etwa in die Mitte der "Schlaufe" platziert werden, nicht am äußeren Rand. Waze berücksichtigt nur Straßen für das Routing, die durch Kreuzungen eingeschlossen sind. Wenn die das Ende des Segments mit der Kreuzung daran in der Mitte der Schlaufe platziert wird, kann sie der Fahrer auch erreichen, egal wie er durch die Schlaufe fährt. Eine Ausnahme ist dabei das Beispiel im nächsten Bild. Die Cul-de-sac im Bild unten sollte wie eine normale Sackgasse ohne Schlaufe behandelt werden, die kleine Insel in der Mitte kann ignoriert werden. : [[Image:Jct_cul-de-sac_island_ex.png|200px]] Hier in diesem Beispiel ist es besser, die Straße an den äußeren Rand der kleinen Insel in der Mitte zu platzieren. So kann der Fahrer die Kreuzung am Ende auch erreichen. : [[Image:Jct_cul-de-sac_island_ex_road.png|200px]] Wenn die Cul-de-sac eine sehr große Schlaufe am Ende besitzt, kann es besser sein diese mit einer [[#Schlaufen|Schlaufe]] zu versehen. Faustregel: Stell Dir vor, Du stehst am Ende einer Cul-de-sac, kannst Du dann mit Sicherheit sagen ob es sich um eine Cul-de-sac handelt, oder sieht es aus wie zwei verschiedene Straßen? Wenn eine Insel da ist und Du nicht sicher bist, ob eine Schlaufe wichtig ist, lass sie weg! Wenn Kartenfehler entstehen "Fehlende Straße" füge eine Schlaufe hinzu. ==== Schlaufen ==== Eine Schlaufe führt in der Regel in einer Richtung vom Ausgangspunkt (Kreuzung) an diesen zurück. '''Eine wichtig Regel für Editoren lautet:''' Ein Segment kann nicht mit sich selbst durch eine Kreuzung verbunden werden! <br> Die Schlaufe muss zwingend durch eine Kreuzung unterbrochen sein, oder durch zwei Segmente gezeichnet werden. Der Routing-Server hat Probleme eine Route aus einer "kaputten" Schlaufe zu finden. Praktisch wäre da natürlich, wenn eine weitere Straße aus der Schlaufe heraus führen würde und die Schlaufe so in zwei Teile unterteilen würde. Der Ort, wo eine zusätzliche Kreuzung platziert wird ist nicht entscheidend, aber die meisten Editoren platzieren sie etwa in der Mitte. : [[Image:Jct_loop_bulb.png]] [[Image:Jct_loop_square.png]] '''Anmerkung:''' Es ist sehr leicht für Editoren vermeintlich unnötige Kreuzungen zu finden und diese zu löschen. Ein Möglichkeit um dies zu verhindern ist: Einen Weg der aus der Schlaufe führt zu finden und so eine 3-Wege-Kreuzung zu erstellen. Die Wahrscheinlichkeit, dass diese gelöscht wird ist kleiner. '''Anmerkung:''' Der Waze Map-Editor speichert keine Schlaufe, die nicht durch eine zusätzliche Kreuzung unterteilt ist. Wenn Fehler beim Speichern auftreten, versuche folgendes: Wenn die Straße und die Schlaufe daran den selben Namen haben: * Wähle Schlaufe und Straße aus * Klick das Brücken-Symbol an. Ein Ende der Schlaufe wird getrennt * Unterteile die Schlaufe durch eine Kreuzung * Verbinde das Ende der Schlaufe wieder * Setze die Abbiegungen Wenn die Straße und die Schlaufe daran nicht den selben Namen haben: * Zeichne eine neue Straße und verbinde sie auf die Kreuzung * Gib der Straße den selben Namen wie der Loop hat * Wähle die Schlaufe und die neu gezeichnete Straße aus * Klick das Brücken-Symbol an. Ein Ende der Schlaufe wird getrennt * Unterteile die Schlaufe durch eine Kreuzung * Verbinde das Ende der Schlaufe wieder * Setze die Abbiegungen In diesem [http://www.youtube.com/watch?v=a7yAzG7HElw Video auf YouTube] wird die zweite Methode beschrieben. === Kreisverkehre === : [[Image:Jct_roundabout.png]] Lies die Seite [[Erstellen_und_bearbeiten_eines_Kreisverkehrs|Erstellen und bearbeiten eines Kreisverkehrs]], um mehr Informationen zu dieser speziellen Kreuzung zu erhalten. === Abbiegespuren === : [[Image:Jct_at_grade_keep.png]] Diese Segmente sind keine Ramps! Pass auf die Abbiegeverbote auf. Lies die Seite [[Abbiegespuren]], um mehr Informationen zu dieser speziellen Kreuzung zu erhalten. === Bow tie Kreuzung === Die "Bow tie"-Form einer Kreuzung erlaubt uns die Kontrolle über Kreuzungen mit ein- und zweispurigen Straßen. : [[File:Jct_bowtie.png]] Indem die gesamte Straßenkreuzung auf eine einzige Kreuzung zusammengezogen wird, erhalten wir die Kontrolle über U-Turns (z.B. unerlaubtes Wenden). Wir vermeiden damit kurze Segmente, die eine Kreuzung unnötig verkomplizieren und zu Routing-Problemen führen können. Unser Instinkt sagt uns, dass die Straßenkreuzung, wie sie auch in der Realität erscheint zu zeichnen ist und die Form eines "H" hat. Wird die Straßenkreuzung jedoch wie ein H gezeichnet und sind die Abbiegungen in alle Richtungen erlaubt, können unerlaubte Wendungen nicht vermieden werden. Aber wenn die Straßenkreuzung als Bow tie gezeichnet wird, kann durch die Abbiegeverbote jede Wendung einzeln kontrolliert werden. Zusätzlich kann das mittlere Segment des H zu Problemen mit den Ansagen in der App führen, wenn die angeschlossenen Segmente auf beiden Seiten der kreuzenden Straße andere Namen besitzen. Daher muss das mittlere Segment unbenannt bleiben. Auch wenn im Karteneditor mit der Funktion "Gesamte Straße auswählen" Segmente ausgewählt werden, wird das mittlere Segment ausgelassen. Als letztes noch, Waze hat auch Schwierigkeiten bei der Erfassung von Durchschnittsgeschwindigkeiten für kurze Segmente. Vor allem dann, wenn der Verkehr nicht über das gesamte Segment innerhalb der Kreuzung verläuft, was bei grösseren Straßenkreuzungen passieren kann. Im obigen Beispiel läge das mittlere Segment vertikal zwischen den Straßen, aber die Fahrzeuge, die durch diese Kreuzung fahren, biegen eher in einem 45°-Winkel ab. Dazu kommt noch die Ungenauigkeit der GPS-Chips, was dazu führt, dass die kleinen Segmente nicht in jedem Fall vollständig abgefahren werden. '''Hinweis:''' Achte auf die Geometrie der Bow tie. Wenn der Winkel zu steil ist (45 Grad oder mehr), werden entlang der einspurigen Segmente unnötige Ansagen produziert. '''Hinweis:''' Wenn das mittlere Segment lang ist oder dem Verkehr erlaubt anzuhalten, kann eine Bow tie nicht unbedingt die beste Lösung sein. In diesem Fall rechtfertigt ein H die Form, wenn die einspurigen Segmente zu weit von ihrer physischen Position entfernt wären, um sie in einer Kreuzung zu vereinen. ''Bow tie:<br> http://en.wikipedia.org/wiki/Bow_tie''<br> ''Mapcat, ein Editor aus den USA hat diese From als erster auf der Waze-Karte gezeichnet. Er ist sozusagen der Erfinder dieser Technik.'' == Rampen == [[Glossar|Ramps]] haben einen speziellen Zweck in Waze. Sie sind dafür da um Minor Highways, Major Highways, und Freeways mit Straßen zu verbinden, wo keine ebenerdige Abbiegespuren vorhanden sind. === Wo sollen Rampen eingesetzt werden === Folgende Bedingungen müssen erfüllt sein: # Zwei Straßen kreuzen über- oder untereinander ohne ebenerdige Abbiegespuren # Mindestens eine Straße hat den folgenden Typ ## Minor Highway ## Major Highway ## Freeway ## Ramp #Ausnahme Deutschland: In Autobahnkreuzen werden die Verbindungsstücke, also Ohren und Parallelfahrbahnen, ebenfalls als Ramp klassifiziert. Wenn das obige nicht zufriedenstellend ist, versuche mit ebenerdigen [[Abbiegespuren]] zu arbeiten. === Wie komplex sollten Ramps sein? === Regel #1 einfacher ist besser. Wenn die Abstände der Straßen (am Anfang und am Ende der Ramp) nicht groß genug sind, ist ein einziges Segment und eine Kreuzung alles, was benötigt wird. Die Existenz von Markierungen, Beton- oder Grasflächen ist kein Grund, separate Spuren zu zeichnen. : [[Image:Jct_ramp_no_split.png]] Wenn Straßen am Ende der Ramps deutliche Abstände aufweisen, unabhängig von der Existenz jeglicher Inseln, sollte mehrere Rampes verwendet werden. : [[Image:Jct_ramp_split.png]] == Kreuzungen mit Highway- und Freeway-Segmenten == Hier handelt es sich um Kreuzungen mit Minor Highway, Major Highway und Freeway und natürlich Ramp-Segementen. Spezifische Beispiele folgen später. Alle diese Beispiele verwenden eine grundlegende Basis, die ​​hier erklärt wird. Wenn Du nicht sicher bist, welche Straßentypen Du verwenden sollst, schau in die länderspezifischen Wikis, um mehr Informationen zu erhalten. ==== Ausfahrten an Highway- und Freeway-Segmenten ==== Standard-Situation bei Ausfahrten: Wenn in einer geraden Richtung gefahren wird und eine Abbiegeanweisung nur für die Ausfahrt benötigt wird. Wenn Navigationsanweisungen für beide Richtungen erforderlich sind, schau Dir den Abschnitt [[#Wayfinder-Segmente|Wayfinder Segmente]] an weiter unten. ===== Struktur ===== : [[Image:Jct_fwy_exit.png]] [[Image:Jct_maj_exit.png]] [[Image:Jct_min_exit.png]] Standard-Situation bei Ausfahrten müssen folgendes aufweisen: # Das Segment vor und nach der Kreuzung muss Freeway, Major Highway oder Minor Highway sein. # Der Anfangswinkel des Segments nach der Kreuzung muss in etwa einen 0-Grad Winkel bilden mit dem Segment vor der Kreuzung. # Das Ausfahrts-Segment muss ein Ramp-Segment sein. # Das wegführende Ramp-Segment muss einen Anfangswinkel zwischen 20 und 30 Grad besitzen. Wenn dies alles erfüllt ist, wird die Abbiegeanweisung "Ausfahrt rechts/links" für das Ramp-Segment generiert und keine Anweisung, um geradeaus auf den Highway/Freeway-Segmenten zu fahren. ===== Benennung ===== Die Highway/Freeway-Segmente vor und nach der Kreuzung haben den selben Namen. Das Ramp-Segment wird nach den Konventionen im Wiki Deines Landes benannt. ==== Verzweigung mit Highway/Freeway-Segmenten (Splits) ==== Ein Highway/Freeway Split bildet eine Verzweigung an einer Kreuzung mit zwei anderen Highway/Freeway-Segmenten und es gibt keine offensichtlich gerade Richtung für den Fahrer. ===== Struktur ===== : [[Image:Jct_fwy_fwy_split.png]] Um eine Navigationsanweisung für '''beide''' Richtungen der Abzweiger zu erhalten, muss folgendes erfüllt sein: # Alle Segmente müssen einen der Highway/Freeway-Typen haben. # Alle Segmente müssen unterschiedlich benannt sein. # Die zwei Segmente nach der Kreuzung müssen einen Anfangswinkel zwischen 20 und 30 Grad besitzen. Wenn dies alles erfüllt ist, wird die Navigationsanweisung '''"Rechts halten"''' oder '''"Links halten"''' generiert und der Name der verzweigenden Segmente wird angesagt. ===== Benennung ===== Die wichtigste Regel ist, dass alle 3 Segmente an der Kreuzung müssen unterschiedliche Namen haben. Dies kann über zwei Möglichkeiten erreicht werden: # Nur durch die Straßennamen. Dies ist die einfachste Situation, denn sie beinhaltet alles damit der Split funktioniert. # In Zusammenhang mit Zeichen und [[#Wayfinder-Segmente|Wayfinder-Segmenten]]. Wenn ein Abzweiger den selben Namen trägt wie das Segment vor der Kreuzung, müssen wir einen Unterschied zwischen den zwei Segmenten herstellen. Wenn "Highway A" von "Highway B" abzweigt und "Highway A" dabei zum zweiten Abzweiger wird, dann sollten Wayfinder-Segmente verwendet werden. ==== Wayfinder-Segmente ==== Es ist manchmal notwendig bei komplexen [[#Ausfahrten_an_Highway-_und_Freeway-Segmenten|Ausfahrten an Highway- und Freeway-Segmenten]] und [[#Verzweigung_mit_Highway.2FFreeway-Segmenten_.28Splits.29|Verzweigungen]] dem Fahrer zusätzliche Informationen zu liefern. Beispiele solcher Situationen: * '''Spurverengungen''' - Ein Highway hat kilometerlang 3 Spuren, aber nur 2 Spuren führen nach einer Kreuzung weiter. *'''Inkonsistente Beschilderung''' - Highway führt weiter als nummerierte Straße, aber auf den Schildern sind nur Namen angezeigt. *'''Nicht offensichtliche Fortsetzung''' - In einem Land mit Rechtsverkehr verlässt man die Straße auf die linke Seite, der weiterführende Verkehr ist auf der rechten Seite. In diesen Fällen benötigen wir ein kurzes Wayfinder-Segment, welches nach der Beschilderung benannt wird. Ein Wayfinder-Segment muss mindestens 5 Meter lang sein. Es gibt zwei Methoden, um dies zu bewerkstelligen: Mit Highway/Freeway-Segmenten oder mit Ramp-Segmenten. * '''Highway/Freeway-Segmente''' ** Pro: Bietet eine durchgängig gerenderte Linie auf der Karte ohne Unterbrechungen ** Pro: Fügt keinen Routing-Penalty hinzu für den Übergang zum Ramp-Segment (obwohl wir nicht wissen, wie viel Einfluss - wenn überhaupt - dieser in Wirklichkeit hat) ** Contra: Der lange Name des Segments kann auf der Karte unübersichtlich sein ** Contra: Das Segment wird im Editor schwer identifizierbar, da es sich mit den Freeway-Segmenten des Hauptzweigs vermischt. ** Anmerkung: Wird '''"Links halten"''' und '''"Rechts halten"''' Anweisung generieren * '''Ramp-Segmente''' ** Pro: Alle langen Namen werde nicht angeziegt auf der Karte ** Pro: Forciert den Zoom auf dem Client, um die Verzweigung anzuzeigen ** Contra: Fügt einen Routing-Penalty hinzu für den Übergang zum Ramp-Segment (obwohl wir nicht wissen, wie viel Einfluss - wenn überhaupt - dieser in Wirklichkeit hat) ** Contra: Kann als unterbrochene Linie auf der Karte erscheinen ** Anmerkung: Wird '''"Links halten"''' und '''"Ausfahrt rechts"''' Anweisungen ansagen in Ländern mit Rechtsverkehr und '''"Ausfahrt links"''' und '''"Rechts halten"''' in Ländern mit Linksverkehr In beiden Fällen '''müssen''' die beiden abzweigenden Segmente identische Straßentypen besitzen. Alle drei Segmente müssen unterschiedliche Namen haben. Hier zweigt Highway Y ab von Highway X. Durch die Benennung der Segmente mit den verfügbaren Informationen auf den Schildern an der Verzweigung, haben wir eine Einzigartigkeit erreicht und vermitteln zusätzliche, nützliche Informationen (der Ziel-Städte) an den Fahrer. Wir können die gewünschten Ergebnisse auf zwei Arten erreichen. <br> '''Mit Freeway-Segmenten:''' [[Image:Jct_fwy_fwy_wayfinder_fwy.png]] '''Mit Ramp-Segmenten''' (gleiche Benennung wie im oberen Bild): [[Image:Jct_fwy_fwy_wayfinder_rmp.png]] Manchmal ist es auch notwendig, einen Wayfinder an einer Ausfahrt zu verwenden, wenn der Fahrer eine Vorankündigung braucht, dass nur einige Fahrspuren geradeaus führen. Wieder kann das auf zwei Arten erreicht werden: '''Mit Freeway-Segmenten''' für die Verzweigung: [[Image:Jct_fwy_rmp_wayfinder_fwy.png]] '''Mit Ramp-Segmenten''' (wieder gleiche Benennung wie im oberen Bild): [[Image:Jct_fwy_rmp_wayfinder_rmp.png]] Als Faustregel für die Wayfinder-Segmente gilt: Eine Länge von 15 bis 20 Meter. Das hält die Segmente kurz und sie fallen nicht so auf im Client. Dennoch sind sie gross genug, damit wir sie im WME finden und verändern können. ==== Verzweigungen mit Ramp-Segmenten ==== Wenn Ramp-Segmente Verzweigen, wird in allen Fällen eine '''"Ausfahrt rechts"''' und '''"Ausfahrt links"''' Anweisung angesagt, mit den Namen der abzweigenden Segmente. ===== Struktur ===== : [[Image:Jct_ramp_ramp_split.png]] ===== Benennung ===== Wenn Ramp-Segmente nicht benannt sind, wird der Name des nachfolgenden Segments angesagt. Im Bild oben kann das Segment vor der Kreuzung unbenannt bleiben, wenn die zwei Ramp-Segmente, die verzweigen benannt wurden. Die Navigationsanweisung die angesagt wird vor dem ersten Segment, wird den Namen der Ramp, die nach der Kreuzung folgt ansagen. '''Beispiel:''' Die zwei Ramp-Segemente nach der Kreuzung sind mit "Ziel links" und "Ziel rechts" benannt. Das Segment vor der Kreuzung ist unbenannt. Wenn Du nun auf das unbenannte Segment rechts ausfahren musst und weiterfahren willst nach "Ziel links" wird die Ansage lauten: * '''Ausfahrt rechts''' nach '''Ziel links''' * '''Ausfahrt links''' nach '''Ziel links''' Unbenannte Ramp-Segmente zu verwenden ist sehr hilfreich, um die nötigen Ansagen da zu generieren, wo sie auch benötigt werden. So lange die Namen der beiden Ramp-Segmente, die verzweigen ausgeschildert sind, bei der Ausfahrt des ersten Segments. '''Gutes Beispiel für unbenannte Ramp-Segmente:''' * Schild bei der ersten Ausfahrt: Nach Stadt A und Stadt B * Schild nach links: Nach Stadt A * Schild nach rechts: Nach Stadt B Ergebnis: Das unbenannte erste Ramp-Segment wird dem Fahrer eine genaue Navigationsanweisung geben. '''Schlechtes Beispiel für unbenannte Ramp-Segmente:''' * Schild bei der ersten Ausfahrt: Richtung Zentrum * Schild nach links: Richtung Zentrum * Schild nach rechts: Richtung Bundesstraße Ergebnis: Das unbenannte erste Ramp-Segment kann verwirrend sein für den Fahrer, da nicht beide Ziele auf dem ersten Ausfahrts-Schild ersichtlich sind. In diesem Fall sollte das erste Segment benannt werden. '''Modifizierte Variante für unbenannte Ramp-Segmente:''' * Schild bei der ersten Ausfahrt: Ausfahrt 70A-B nach Stadt A und Stadt B * Schild nach links: Nach Stadt A * Schild nach rechts: Nach Stadt B * Name des Ziels nach links in Waze: Ausfahrt 70A: Stadt A * Name des Ziels nach rechts in Waze: Ausfahrt 70B: Stadt B Ergebnis: Wenn modifizierte Namen für die Ziel-Ramps verwendet werden, können wir Informationen aus zwei Sätzen von Schildern kombinieren, um dem Fahrer eine Vorankündigung zu liefern, womit er sich auf eine Verzweigung vorbereiten kann. == Spezialfälle == === Übergangs-Kreuzungen === Eine Übergangs-Kreuzung(Transition Node) ist eine im Client nicht dargestellte Kreuzung. : [[Image:Jct_transition.png]] [[Image:Jct_transition_90.png]] Beispiele, wie Übergangs-Kreuzungen verwendet werden: # Straßenname ändert # Um Stadtgrenzen zu definieren # Wenn die Straßenrichtung ändert # Teile einer [[#Schlaufen|Schlaufe]] Es gibt viele solche Kreuzungen auf der Base-Map(z.B. Brücken), oder sie wurden nach der Löschung eines Segments hinterlassen. Wenn Du '''sicher''' bist, dass diese Kreuzungen nicht verwendet werden, solltest Du sie entfernen von der Karte. Dies vereinfacht die Karte, eliminiert Abbiegungen, die bearbeitet werden müssen und zusätzliche Kreuzungen, die das Routing nur negativ beeinflussen. Nach der Löschung entsteht auch ein Geometrie-Punkt, falls dieser nicht benötigt wird, entferne ihn auch gleich. === Nicht befahrbare Segmente === In gewissen Situationen ist es notwendig, nicht befahrbare Segmente hinzuzufügen, damit korrekte Navigationsanweisungen entstehen. ==== Konkret ==== Ein gutes Beispiel ist das Ende einer Autobahn. Nehmen wir an, die Autobahn befindet sich im Bau, oder ist nach einer Ausfahrt gesperrt. Wenn nun ein Freeway-Segment direkt in ein Ramp-Segment führt und dahinter keine Fortsetzung der Freeway-Segmente existiert, wird auch keine korrekte Navigationsanweisung folgen. Wenn wir nun eine kleine Fortsetzung an das letzte Freeway-Segment hängen, gibt dies dem Routing-Server eine Kreuzung, für die eine korrekte Ausfahrts-Ansage produziert wird am Ende der Autobahn. Umgekehrt, wenn keine Ansage folgen soll und es keinen anderen Weg gibt am Ende einer Autobahn, müssen wir sicherstellen, dass keine Segmente nach der letzten Kreuzung vorhanden sind. === Versetzte Straßen === Manchmal findet man Straßen, die zwar kreuzen, aber nicht genau auf einer Linie liegen. : [[Image:Jct_4_offset.png]] In solchen Situationen gilt es ein paar Sachen zu beachten # Kreuzen sie sich wirklich auf einer Linie? Wenn ja, müssen wir die Kreuzung in eine 4-Wege-Kreuzung ändern. # Kreuzen sich die Straßen fast auf einer Linie? Wenn eine Navigationsanweisung gegeben werden kann, ohne dass Abbiegungen angesagt werden, dann kann man eine 4-Wege-Kreuzung daraus erstellen. Um dies zu erreichen muss man die Straßen ein wenig verschieben, damit sie nicht mehr der Mittellinie folgen bei der Kreuzung. Damit wieder ein 90-Grad Winkel an der Kreuzung entsteht, müssen wir, wie im [[#Kreuzung_mit_vier_Fahrtrichtungen|Abschnitt 2.4]] beschrieben, einen zusätzlichen Geometrie-Punkt hinzufügen. Damit besser gearbeitet werden kann an der Kreuzung, kann der Zoom erhöht werden im WME, vor allem damit die Winkel richtig positioniert werden können.<br/>[[Image:Jct_4_offset_align.png]] [[Image:Jct_4_offset_align_ex.png]]<br/> # Zuletzt, ist wirklich eine Trennung der Einmündungen vorhanden? Wenn ja und wir die Anweisung "links abbiegen" und dann "rechts abbiegen" gebrauchen können, dann sollten wir die Kreuzung so belassen.<br />[[Image:Jct_4_offset_ex.png]]<br />Die GPS-Chips in den Geräten können sehr ungenau sein. Dabei kann es vorkommen, dass der Fahrer die kurzen Segmente überspringt, was automatische Kartenfehler hervorruft, oder auch in einer Neuberechnung der Strecke enden kann. Daher sollten wir sehr kurze Straßen-Segmente vermeiden und es ist besser die Straßen so weit wie möglich auseinander zu ziehen. Dies verlängert die kurzen Segmente zwischen den Seitenstraßen.<br /> [[Image:Jct_4_offset_sep_ex.png]] =Hilfsmittel= Die zwei besten Helfer ("WME Junction Angle info" und "WME Route Tester") zum bestimmen der Winkel und testen der bestehenden Wege und Routen befinden sich hier auf der Seite: [[Community Plugins, Extensions and Tools]]. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] b0520dfac4ff9bda76b3e50b1aa5c7ae8006b831 0 89 12015 2017-10-29T20:50:50Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] In der Waze-Karte gilt das KISS-Prinzip. Grundsätzlich sollten keine Abbiegespuren eingezeichnet w…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] In der Waze-Karte gilt das KISS-Prinzip. Grundsätzlich sollten keine Abbiegespuren eingezeichnet werden. Abbiegespuren werden nur dann eingezeichnet, wenn sie nach den folgenden Ausführungen nötig sind. == Soll eine zusätzliche Verbindung auf der Karte erscheinen? == Am wichtigsten ist festzustellen, ob wir überhaupt eine zusätzliche Verbindung in Form einer ebenerdigen Abbiegespur benötigen, in aller Regel bedarf es dieser nicht! Der Fahrer, der eine Kreuzung erwartet, hat durch Waze normalerweise schon mindestens eine Meldung zum baldigen Abbiegen erhalten, und man kann davon ausgehen, daß er die vorhandenen Abbiegemöglichkeiten rechtzeitig erkennt. Für fast alle Kreuzungen genügt es, dem Fahrer zur richtigen Zeit die Abbiegeinformation zu geben, die er benötigt, wozu eine einfache Kreuzung ohne speziell angelegte Abbiegerspuren völlig ausreicht. Nur in wenigen Situationen benötigen wir wirklich separate Spuren: * wenn die Abbiegespur sehr früh vor der Kreuzung beginnt und durch eine Rabatte o. dgl. so getrennt wird, daß kein Spurwechsel mehr möglich ist * wenn die Gefahr besteht, daß der Fahrer die Abbiegeinformation zu spät erhält und er die Spur nicht mehr rechtzeitig vor der Kreuzung erreichen kann * Wenn an einer Kreuzung ein Kartenfehler entsteht – ''[[WME_Map_Problems|Map problem]]: Missing road, The roads are too far apart from each other and most likely a road is missing in between (fehlende Straße zwischen zwei Verbindungen)'' – und die Abbiegespur weit genug vor der Kreuzung beginnt. * Wenn Du Area-Manager bist und entsprechende Hinweise von anderen Anwendern über zu späte Sprachanweisungen erhältst. Diese Fälle werden nur selten vorkommen, da die meisten Richtungsänderungen schon 800 m vorher angekündigt werden. Im Zweifel also weglassen. Denn jede Spur verkompliziert die Karte und bereitet Dir Mehraufwand beim Kontrollieren der zulässigen Abbiegungen, Richtungen und der Benennung. Last but not least verzögert das auch die Routenberechnung. Mach es so einfach wie möglich! == Klassifizierung == Ebenerdige Abbiegespuren sind nicht als Ramps zu deklarieren, diese sollen in der Regel für Autobahn-Auf- und -Abfahrten reserviert bleiben. (Siehe dazu auch [[#Ausnahmen|Ausnahmen]].) Die Abbiegespuren haben den tiefsten Straßentyp, aller vorkommenden Straßen. (Wenn bspw. eine Primary Street einen Major Highway kreuzt, ist für die Verbindungen der Typ "Primary" zu vergeben.) Beispiel: [[Image:At-grade_example1.jpg]] Hier kann man auch schön sehen, daß links oben keine Abbiegespur angelegt ist, weil keine Verkehrsinsel vorhanden ist und sie hier keinesfalls benötigt wird. == Benennung == In den meisten Fällen reicht es aus, den Spuren keinen Straßennamen zuzuweisen, da die Navigationsanweisungen einfach den Namen des nächsten Segments, zu dem die Spur führt angeben wird. Falls im Einzelfall Wegweiser an der Kreuzung den Fahrer verwirren könnten oder gar widersprüchliche Aussagen enthalten, könnte eine sinnvolle Benennung hilfreich sein. == Geometrie == Die Seite [[Kreuzungen]] zeigt, wie die Geometrie am sinnvollsten zu gestalten ist, um die besten Navigationsweisungen und Sprachausgaben zu erzielen. Schau Dir diesen Artikel auf jeden Fall an. == Ausnahmen == === Die Spur ist eine ausgeschilderte, numerierte Ausfahrt === '''Beispiel:''' Die Ausfahrt 10 des Garden-State-Parkway in Cape May Court House, New Jersey, USA. Der Garden-State-Parkway ist größtenteils ein Maut-Freeway (toll-road) der von Norden nach Süden durch New Jersey führt. In nördlicher Richtung ist die Linksaabiegerspur die Ausfahrt 10A und die Rechtsabbiegerspur die Ausfahrt 10B. Und in südlicher Richtung umgekehrt, 10A führt nach Westen und 10B nach Osten. [[Image:GSP_10A.jpg]][[Image:GSP_10B.jpg]] [[Image:GSP_10.jpg]] == Fazit == Bevor Du eine ebenerdige Abbiegerspur anlegst, prüfe genau, ob sie wirklich erforderlich ist. Ggf. ist auch eine Diskussion im Forum hilfreich. Wenn Du unbearbeitete Kreuzungen auf der Karte findest, versuche die meist unnötig angelegten Spuren zu entfernen (s. auch [[Base_Map_1.0|Base Map 1.0]]), denn sie helfen niemandem wirklich. Tip: mit dem GPS-Layer kannst Du sehen, ob die Kreuzung stark frequentiert ist. Wenn nur wenige oder gar keine Spuren über sie führen, dann ist Einfachheit oberstes Gebot! Lösche die meist von der Base-Map angelegten doppelten Spuren und Abbiegespuren, setze den Kreuzungsmittelpunkt sinnvoll in die Mitte, auch wenn eventuell kleine Rabatten angelegt sind - sie sind in aller Regel so schmal, daß sie für uns nicht relevant sind! <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 049344c0cd73421b88e6f829e52152406b29da77 0 8 12016 10597 2017-10-29T20:55:12Z Popel22 24 /* Wichtiges zum Thema Kartenbearbeitung */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Blitzer einpflegen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Base Map 1.0]] * [[Der Area Manager]] ==Seiten auf Englisch== * [[How Waze determines turn / keep / exit maneuvers]] * [[Limited Access Interchange Style Guide]] * [[Navigation problems]] * [[Small Detour Prevention Mechanism]] * [[Community Plugins, Extensions and Tools]] * [[Classification of crossings]] * [[Scheduled_Restrictions|Scheduled Restrictions]] * [[Battery Usage]] ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Hilf mit Waze zu verbessern]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] 1592c5cc96291e7b177a2907488cfd7f9757488a 12022 12016 2017-10-29T21:26:24Z Popel22 24 /* Wichtiges zum Thema Kartenbearbeitung */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Base Map 1.0]] * [[Der Area Manager]] ==Seiten auf Englisch== * [[How Waze determines turn / keep / exit maneuvers]] * [[Limited Access Interchange Style Guide]] * [[Navigation problems]] * [[Small Detour Prevention Mechanism]] * [[Community Plugins, Extensions and Tools]] * [[Classification of crossings]] * [[Scheduled_Restrictions|Scheduled Restrictions]] * [[Battery Usage]] ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Hilf mit Waze zu verbessern]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] 16b8ba5d36fe786dc43feb8f4bd7f28dfed33c60 12025 12022 2017-10-29T21:28:21Z Popel22 24 /* Wichtiges zum Thema Kartenbearbeitung */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== * [[How Waze determines turn / keep / exit maneuvers]] * [[Limited Access Interchange Style Guide]] * [[Navigation problems]] * [[Small Detour Prevention Mechanism]] * [[Community Plugins, Extensions and Tools]] * [[Classification of crossings]] * [[Scheduled_Restrictions|Scheduled Restrictions]] * [[Battery Usage]] ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Hilf mit Waze zu verbessern]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] 3ea87cfe857d5321c627ff2372280651711a5fbd 0 90 12017 2017-10-29T20:55:34Z Popel22 24 Die Seite wurde neu angelegt: «{{mbox|type=important|text=Abbiegeanweisungen sind eine zusätzliche Möglichkeit Ansagen zu erzwingen oder zu unterdrücken und nur dort anzuwenden wo es erford…» wikitext text/x-wiki {{mbox|type=important|text=Abbiegeanweisungen sind eine zusätzliche Möglichkeit Ansagen zu erzwingen oder zu unterdrücken und nur dort anzuwenden wo es erforderlich ist. Es gibt keine Anweisung oder keinen Grund bestehende Strukturen wie Wayfinder zu überschreiben.}} <br /> {{TOC}} {{mbox|type=neweditor|text=Insbesondere neuen und Jungeditoren wird empfohlen sich Rat über die Notwendigkeit dieser zusätzlichen Ansagemöglichkeiten bei erfahrenen Editoren einzuholen.}} ==Wann sollen/können die Ansagemöglichkeiten verwendet werden:== ===erwünschte Ansage / unterdrückte Ansage=== Wenn durch einfache und/oder normale Edits (und deren Regeln z.b. bzgl. Geometrie) nicht die erwünschten oder unerwünschten Ansagen kommen. Unerwünschte treten z.b. auf wenn 3 unterschiedliche Straßenkategorien auftreten. (weitere Beispiele unten auf dieser Seite) ===U-turn=== Diese Anwendung ist für Einbahnstraßen geeignet wenn wieder in die Gegenrichtung gefahren werden soll/kann. Statt "links abbiegen" erfolgt die Ansage wenden. ===vereinfachter Wayfinder=== Durch die Pfeilansagen kann ein einfaches rechts/links halten generiert werden. Es wird das Folgesegment angesagt (insofern ohne Richtungsangabe wenn nicht angegeben). Insbesondere kann diese Form der erzwungenen Ansagen unerwünschte Fehlrouting (Detours) vermeiden helfen. ==Wann diese Ansagen NICHT verwendet werden sollen== ===Normale Straßen und Kreuzungen=== Die Ansagen sind sorgfältig nur dort anzuwenden wo es sinnvoll ist. Um zu vermeiden das permanent Ansagen kommen dürfen diese nicht auf normalen Straßen und Kreuzungen angewendet werden. ===Komplexe Strukturen=== Komplizierte Kreuzungen oder auch Wayfinder sollten wie editiert belassen werden sofern sie durch ihre Darstellung oder Benennung eindeutig sind. Das überschreiben mit einer Ansage sollte auch hier nur bedacht ausgeführt werden. ==Wie editieren?== [[File:Wme_turn_override_hover2.png]] {{clear}} Wenn man ein Segment angewählt hat und mit dem Mauszeiger langsam über einen Pfeil "fährt" klickt man auf den erscheinenden Lautsprecher. Es öffnet sich ein Fenster mit den Auswahlmöglichkeiten: ===Verfügbare Pfeilansagen=== [[File:Fenster_Anweisungen.png]] {{clear}} *Von Waze ausgewählt = Pfeilansage nicht erzwungen, Ansagen erfolgen entsprechend den editierten Segmenten und deren Regeln *Keine = es erfolgt keine Ansage (mehr) *Links abbiegen *Rechts abbiegen *Links halten *Rechts halten *Weiter = für "Geradeaus", noch nicht in der app verfügbar *Links ausfahren *Rechts ausfahren *Wenden Editierte Pfeilansagen sind daran zu erkennen das das Lautsprechersymbol am Pfeil die Farbe von [[Image:Wme_override_speaker_icon.png]] Cyan nach [[Image:Wme_override_speaker_icon_active.png]] Orange gewechselt hat. Wenn "Von Waze ausgewählt" wird ist keine Ansage editiert und das Lautsprechersymbol ist (wieder) Cyan. ==Beispiele== * Ansage "Keine" [[File:Anweisung_Keine.png]] {{clear}} Hier kommt durch die 3 unterschiedlichen Straßenkategorien (Landes, Privatstraße + Rampe) von Westen her eine Ansage "links halten". Da aber kein weiterer Spurwechsel nötig (oder im Beispiel nicht erlaubt) ist wurde die Ansage über den Pfeil mit "Keine" unterdrückt. * Ansage "Weiter bei Autobahnwechsel / Spurwechsel erforderlich" [[File:Anweisung_Weiter_AB.png]] {{clear}} In Autobahnkreuzen, -dreiecken oder teils auch Ausfahrten wird die Ansage "Weiter" auf der Geradeausfahrt editiert wenn: - der Autobahnname wechselt (im Beispiel Richtung Norden A1 zu A255) - ein Spurwechsel erforderlich ist weil mindestens eine Fahrbahn in eine Ausfahrt führt * Ansage "Weiter bei Geradeausfahrten" [[File:Anweisung_Weiter.png]] {{clear}} Von Süd-West (B26) nach Nord-Ost (A70) würde keine Ansage kommen da es, den Edits nach, nur geradeaus geht. Dadurch wird aber die übernächste erforderliche Abfahrt bereits hier genannt, auch wenn diese etliche Kilometer entfernt ist (was sehr verwirrend ist). Mit der Pfeilansage "Weiter" werden beide Probleme umgangen: die Auffahrt wird an dieser Stelle entsprechend der Rampe angesagt, die übernächste Abfahrt nicht. 2054b08d790ba7dd753c1315bdfaedd31ddd3f73 0 91 12018 2017-10-29T21:23:37Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Eine neue Straße erstellen= Wenn man eine Stelle sieht in Waze, an der keine Straße vorhanden is…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Eine neue Straße erstellen= Wenn man eine Stelle sieht in Waze, an der keine Straße vorhanden ist aber eine sein sollte, kann man diese bequem am Karteneditor erstellen. Es ist zu Bedenken, dass die Karte im Waze Map-Editor sich nicht in jedem Fall an der richtigen Stelle befindet, deshalb auch auf die GPS-Punkte achten! Im folgenden Beispiel werden wir nun eine Straße einzeichnen. [[Image:Strasse_hinzufügen_gegend.png|400px]] Zuerst bewegt und zoomt man die Karte so, dass eine gute Ansicht auf den Kartenausschnitt möglich ist, wo die Straße eingezeichnet werden soll. So kann man der Straße beim einzeichnen gut folgen und die Kurven auch schön rund zeichnen. Vier wesentliche Schritte sind nötig um eine neue Straße hinzuzufügen: # Zeichnen der Straße inklusive der Kreuzungen an bestehende Segmente. # Eigenschaften erstellen: Namen, Richtung, Sperren etc. # Mögliche Abbiegungen erlauben. # Änderungen speichern. ==Vordefinierte Richtung der Segmente== Ein Segment hat immer eine Richtung, die beim Erstellen des Segments definiert wird. [[File:Erstellungsrichtung.png]] Der Anfangspunkt eines Segments wird durch ein [[File:ACB.png]] auf der Karte dargestellt. Der Endpunkt eines Segments mit [[File:BCB.png]]. Dies hat nichts mit der Fahrtrichtung der Straße selbst zu tun, die wir für das Befahren verwenden in der App. Die Fahrtrichtung kann auch eine Einbahnstraße von [[File:BCB.png]] nach [[File:ACB.png]] darstellen. Daher können bei Mehrfachauswahl von Einbahn-Segmenten mit unterschiedlichen Erstellungs-Richtungen, die Einbahnen niemals miteinander bearbeitet werden. Es wir immer ein Segmente geben, das eine falsche Richtung aufweist. Nur wenn mehrere Einbahn-Segmente die gleichen Erstellungs-Richtungen aufweisen, ist das Bearbeiten mit der Mehrfachauswahl möglich. Dies beschränkt sich natürlich nur auf Einbahnstraßen, bei zweispurigen Segmenten hat die Mehrfachauswahl keine Auswirkungen, man kann alle ausgewählten Segmente auf zweispurig umstellen. ==Neue Straße einzeichnen== [[Image:Strasse_hinzufügen.png|left]] Bewege den Mauszeiger über das grosse Bleistift-Icon auf der rechten Seite in der [[WME_Oberfläche_und_Steuerelemente#Die_Werkzeugleiste|Werkzeugleiste]] und wähle "'''Straße'''" aus. Du kannst auch das [[WME_Schnellstart-Anleitung#Tastaturkürzel|Tastaturkürzel]] "'''i'''" verwenden. Der Mauszeiger besitzt einen kleinen blauen Kreis um anzuzeigen, dass eine neue Straße eingezeichnet wird. Bewege den Mauszeiger an die Stelle, wo Du mit dem Einzeichnen beginnen willst. Mit einem Klick auf ein Segment oder in eine Leere Stelle wird mit dem Einzeichnen begonnen. Du kannst auch dort ansetzen wo die Abzweigung sein soll. Wenn Du ein existierendes Segment berührst mit dem Mauszeiger, leuchtet dieses auf. Wenn Du auf dieses klickst, werden Kreuzungen automatisch gesetzt, wenn Du eine Straße an eine bereits bestehende anhängst. [[Image:Strasse_hinzufügen_gegend.png|700px]] Bewege nun die Maus der Straße entlang, während Du dem Bild oder den GPS-Punkten folgst. Bei jedem Klick wird ein Geometrie Punkt (Kreis) hinzugefügt, an dem Du nach dem Einzeichnen das Segment verschieben kannst, falls dies nötig ist. Wenn Du den Endpunkt der Straße erreicht hast beendet ein Doppelklick das Einzeichnen. Die neue Straße erscheint nun in Orange um anzuzeigen, dass diese noch nicht gespeichert wurde. In diesem Beispiel hängen wir eine Straße an eine bereits bestehende an, wie das Bild unten anzeigt. [[Image:Strasse_hinzufügen_schritt2-4.png|700px]] Im nächsten Beispiel hängen wir eine Straße an die, die wir zuvor erstellt haben. Man kann mehrere Straßen erstellen ohne zwischendurch zu Speichern, was einem sehr viel Zeit spart. [[Image:Strasse_hinzufügen_schritt5.png|700px]] Wenn Du willst kannst Du nun Speichern. Neue Straßen erscheinen im Waze Map-Editor Rot und als Einbahnstraße in der Richtung, in der Du sie erstellt hast. Natürlich sind die Straßen noch nicht fertig und Du musst noch Eigenschaften wie, Straßennamen oder Stadtnamen hinzufügen. Die Eigenschaften der Straße sind wichtig, damit die neue Straße sauber auf der Anwendung erscheint. ==Kreuzung am Ende einer Sackgasse== Damit die Waze-App richtig aus einer Straße heraus navigieren kann, ist eine End-Kreuzung nötig. Ohne diese Kreuzung am Ende einer Straße, wird Waze die Anweisung geben zuerst zur markierten Route zu Fahren. Um eine End-Kreuzung hinzuzufügen, musst Du eine temporäre Straße an die Endpunkte der Sackgasse ziehen. Die hinzugefügte Straße nach dem Verbinden an den Endpunkten musst Du wieder löschen. Der Karteneditor fügt mittlerweile die Kreuzungen automatisch hinzu, solltest Du dennoch Straßen vorfinden ohne End-Kreuzung, füge sie bitte manuell hinzu. Du kannst das Segment leicht verschieben und danach mit der Kreuzung an den ursprünglichen Punkt zurückziehen oder (wie oben beschrieben) mit einem temporären Segment arbeiten. [[Image:Endkreuzung_hinzufügen1.png|700px]] Es gibt für unser Beispiel natürlich zwei Varianten um End-Kreuzungen hinzuzufügen. Entweder Du führst den obigen Schritt zweimal aus oder Du verbindest eine Straße an beide Endpunkte, was das einfachste ist. [[Image:Endkreuzung_hinzufügen2.png|700px]] Wenn noch nicht gespeichert wurde und du die Straße zum erstellen der End-Kreuzungen entfernt hast, sieht es dann so aus, wie auf dem Bild hier. [[Image:Endkreuzung_hinzufügen3.png|700px]] ==Bestätigung durch Eingabe der Eigenschaften== Neue Straßen werden nicht auf der Anwendung zu sehen sein, bevor sie nicht bestätigt wurden. Das heisst: Wenn Du eine Straße erstellst, musst Du mindestens den Stadt- und Straßennamen bearbeiten. Im Waze Map-Editor sind unbestätigte Straßen Rot. Sie können mit dem Editor erstellt oder mit der Waze Anwendung aufgezeichnet worden sein. <br>Um eine Straße korrekt zu Bestätigen: * Weise sie dem richtigen Land zu (wird meist automatisch gemacht, in Grenzregionen kann es mehrere Auswahlen geben). * Weise sie einem Staat zu, wo vorhanden. * Gib den richtigen Ortsnamen ein (Länderspezifische Wikis beachten). * Benenne die Straße. * Setze den richtigen Straßentyp. * Korrigiere wenn notwendig die Richtung. * Verändere die Ebene, wenn es um Über- und Unterführungen geht. Als erstes musst Du das Segment, das Du benennen willst auswählen. Im unteren Bild ist dies eine Einbahnstraße. Wenn Du sie ausgewählt hast, kannst Du im [[WME_Oberfläche_und_Steuerelemente#Reiter_wenn_Segmente_ausgew.C3.A4hlt_sind|Reiter]] die Eigenschaften bearbeiten. Da wir eine zweite Straße angehängt haben, hat sich die erste Straße in zwei Segmente geteilt. Du kannst beide Segmente auswählen und benennen, oder auch bevor Du eine zweite Straße anhängst mit dem Bearbeiten der Eigenschaften beginnen. [[Image:Details_einfügen.png|700px]] [[Image:Details1.png|right]]Um die Eigenschaften zu bearbeiten klicke auf '''Bearbeiten''' und Du kannst mit der Benennung beginnen. <br> Es empfiehlt sich eine Reihenfolge der Eingaben für sich selbst zu bestimmen. <br> Deshalb Nach der Benennung auf '''Übernehmen''' klicken oder zuerst die anderen Eigenschaften komplett bearbeiten. <br><br><br><br><br><br><br><br><br><br> [[Image:Fehler_Land.png|left]]Wenn Du mehrere Segmente bearbeitest musst Du immer ein "Land" bestimmen. Dies gilt für neue Straßen, sowie für Straßen die verschiedenen Ländern zugeordnet sind. Ansonsten erscheint diese Fehlermeldung hier, wenn Du auf "Übernehmen" klickst. <br><br><br><br><br><br><br><br><br><br> [[Image:No_city_no_street.png|right]]Wenn die Straße keinen Namen hat (z.B. Waldstraßen) benutze das Kontrollkästchen "Ohne". Das gleiche gilt für den Straßennamen. Wenn es sich um Private Straßen oder Parkplätze oder andere Straßen handelt, die keinen Namen haben, klicke auf "Ohne" Wenn alles korrekt bearbeitet wurde klicke auf '''Übernehmen''' Danach bestimme den Straßentyp, Richtung und Ebene. Wenn keine Unter- oder Überführungen vorhanden sind, ist die Ebene generell 0. * Beachte, dass "Unbekannt" in der Richtungsangabe nicht davor schützt, dass Waze nicht in eine solche Straße hinein navigiert. "Unbekannt" bedeutet Undefiniert in der '''Base Map'''. Die Richtung ändert, wenn Wazer diese Straße befahren. Das "Sperren" von Straßen schützt nicht davor, dass die Richtung ändert Und wieder, Du könntest jetzt speichern. Aber eine Sache gibt es noch, die Abbiegungen müssen noch bearbeitet werden. ==Abbiegungen bearbeiten== [[Image:Abbiegungen1.png|left]] Wir haben nun die Straßen benannt und bestätigt, doch in welche Richtungen und von woher abgebogen werden darf, musst Du noch bestimmen. Beim Beispiel hier, sind diese Dorfstraßen in allen Richtungen befahrbar. Aber dennoch sind noch rote Pfeile zu sehen. Rot bedeutet Abbiegen nicht erlaubt vom ausgewählten Segment her. Grün bedeutet logischerweise Abbiegen erlaubt. Der eine grüne Pfeil stammt noch von der Straße, die wir als erstes gezeichnet haben. Diese ändert sich nie beim Verbinden von anderen Straßen darauf. <br><br> Waze wird, so wie es jetzt noch aussieht, nicht in diese Richtungen navigieren vom ausgewählten Segment her. Bei Kreuzungen, wo nicht alle Abbiegungen möglich sind, klickst Du normalerweise die roten Pfeile einzeln an und erlaubst so die Abbiegungen. Hier ist das einfachste die Kreuzung auszuwählen und "Alle Abbiegungen erlauben" anzuklicken. So ermöglichst Du das Routing von und in alle Richtungen. Die Abbiegungen können entweder durch die Richtungspfeile oder über die Kreuzung gesteuert werden. Man kann dabei nicht mehrere Kreuzungen auswählen. [[Image:Kreuzung_bearbeitet.png|right]] <br><br> Eine ausgewählte Kreuzung sieht so aus. <br><br><br> [[Image:Abbiegungen_erlauben.png|left]] Wenn eine Kreuzung ausgewählt wird, sind im Reiter die Aktionen sichtbar, die Du bearbeiten kannst. Welcher der Buttons auswählbar ist, hängt vom Status der Kreuzung ab. "Alle Abbiegungen erlauben" oder "Alle Abbiegungen verbieten". Um nun alle Abbiegungen zu erlauben, klicke auf '''Alle Abbiegungen erlauben''' bei beiden Kreuzungen. <br> <br> <br> <br> <br> ==Speichern== Bis jetzt hast du vielleicht schon gespeichert oder auch nicht. Wenn nicht klicke jetzt auf den '''Speichern''' Button oder speichere mit '''Ctrl+s''' Und alle Deine Aktualisierungen werden an den Waze-Server gesendet. Wenn das Speichern beendet ist und keine Fehlermeldungen angezeigt wurden, wird nun das Ergebnis Deiner Bearbeitung zu sehen sein. [[Image:Endergebnis.png|700px]] =Bestehende Straßen bearbeiten= Existierende Straßen oder Segmente zu bearbeiten unterscheidet sich nicht von dem was hier beschrieben wurde bis jetzt. *Für weitere Informationen zur Bearbeitung von Straßen besuche die [[WME Schnellstart-Anleitung]] ==Die Geometrie anpassen== Die Geometrie anzupassen bedeutet eine Straße im Aussehen zu verändern. Du musst dies tun bei Änderungen am Straßenverlauf, oder vielleicht um ein ganzes Gebiet von der Basis-Karte an die richtige Stelle zu versetzen. In der Regel passt man die Straßen der Karte an oder die GPS-Punkte an, was natürlich um einiges genauer ist. Deshalb bei Geometrie-Anpassungen immer auch auf die GPS-Punkte achten. Dazu die Ebene [[WME_Oberfläche_und_Steuerelemente#GPS-Punkte|GPS-Punkte]] einblenden. Die Anweisungen hier gelten für alle Straßen ob nun neu gezeichnete oder bereits bestehende. [[Image:Adjust_geometry_1.png|320px|right]] Wähle zuerst ein Segment aus. Wenn Du nun mit dem Mauszeiger die Straße berührst und diese aufleuchtet, werden die Geometrie Punkte sichtbar. An beiden kannst Du ziehen und die Straße so an den Ort bringen, an den sie gehört. Wenn Du an einem kleinen Punkt ziehst, wird er sich beim loslassen in einen grösseren verwandeln. [[Image:Adjust_geometry_2.png|320px|right]] Um einen Punkt zu löschen, berühre den Punkt mit der Maus und drücke die '''d''' Taste. Das funktioniert nur mit den grösseren, die kleineren Punkte können nicht gelöscht werden. Wenn eine Lange Gerade Straße viele Punkte besitzt macht es Sinn diese auf ein Minimum zu reduzieren. Dies macht das Segment einfacher und es ist leichter darzustellen auf der App. [[Image:Adjust_geometry_3.png|320px|right]] Wenn die Bearbeitung der Geometrie beendet ist speichern nicht vergessen. [http://youtu.be/Pm8zEmlD5bo?hd=1 Hier gibts ein Video dazu]. <br> <br> <br> <br> ==Kreuzungen== Bevor Du Änderungen an Kreuzungen vornimmst schau Dir die Seite über [[Kreuzungen]] an, um Informationen über die beste Vorgehensweise für Kreuzungen zu erhalten. Es gibt Fälle, in denen eine Kreuzung unlogisch erscheint, aber sie ist dennoch wichtig für Navigationsanweisungen. ===Kreuzungen verschieben=== Kreuzungen verschieben ist eine einfache Sache. Man kann sie einfach auswählen und an einen anderen Ort ziehen. Danach müssen nur noch die Geometrie-Punkte der Straßen angepasst werden. [[File:Kreuzung verschieben.png|300px|left]]Wähle als erstes die Kreuzung aus. Ein blauer Punkt erscheint. Dies bedeutet, Du kannst alle Straßen, die an dieser Kreuzung verbunden sind verschieben. Wenn die ausgewählte Kreuzung einen gelben Punkt anzeigt, bedeutet dies in der Regel, dass Du nicht die nötigen [[Rechte_zum_Bearbeiten_der_Karte|Rechte]] hast oder eine Segment ist gesperrt und Du besitzt nicht die nötige Stufe, um die Kreuzung zu bearbeiten. <br clear="all" /> [[File:Kreuzung verschieben2.png|300px|right]]Ziehe nun die Kreuzung an den Ort, wo sie hingehört. Die Winkel in den Segmenten entstehen durch die Geometrie-Punkte, die danach auch noch bearbeitet werden müssen. Achte darauf, dass die Kreuzung nicht eines der Segmente überdeckt, es kann sonst schwieriger werden die Geometrie-Punkte anzufassen und manchmal verbindet sich die Kreuzung auch automatisch mit anderen Segmenten. <br clear="all" /> [[File:Kreuzung verschieben3.png|300px|left]]Die großen Geometrie-Punkte können verschoben werden oder es können weitere hinzugefügt werden, wie [[#Die_Geometrie_anpassen|oben]] beschrieben, um die Straßen an die Realität anzupassen. Passe sie an die Luftaufnahmen oder die [[WME_Oberfläche_und_Steuerelemente#GPS-Punkte|GPS-Punkte]] an. <br clear="all" /> ===Unnötige Kreuzungen löschen=== Es gibt Situationen, wo Du auf der Karte Straßen findest, die durch Kreuzungen unterteilt sind. In der Regel macht dies keine Probleme. Es können aber Probleme durch falsche Abbiegungen auftauchen, was falsche Routen erzeugt oder es kann auch den Bearbeitungsprozess am Karteneditor verlangsamen. Normalerweise müssen alle unnötigen Kreuzungen entfernt werden. Es ist aber dennoch wichtig, die Segmente näher anzuschauen bevor Kreuzungen entfernt werden, um sicher zu stellen, dass sie keinen Zweck erfüllen. {| class="wikitable unsortable" border="1" |- ! Gründe für eine zusätzliche Kreuzung |- style="background:#FFFFFF; color:black" | Die Eigenschaften ändern, z.B. Ortsgrenze, anderer Straßenname, anderer Straßentyp oder Fahrtrichtung |- | Die Segmente sind ein Teil einer [[Kreuzungen#Schlaufen|Schlaufe]] und benötigen eine Extra Kreuzung, um ein korrektes Routing durch die Schlaufe zu ermöglichen. |- |} Wenn Du sicher bist, dass die Kreuzung nicht dahin gehört gibt es drei Möglichkeiten die Kreuzung zu entfernen. * Wenn alle Eigenschaften übereinstimmen, kannst Du die Kreuzung auswählen und auf den Papierkorb in der Werkzeugleiste klicken oder das Tastaturkürzel "Del" verwenden. ''Anmerkung: Segmente mit Richtung "Unbekannt" müssen zuerst eine Richtung erhalten.'' * Du kannst sie mit der Brückenfunktion entfernen. Dadurch werden die Segmente vereint und die Ebene erhöht sich um eine Stufe, passe die Ebene danach wieder an. * Du kannst die Kreuzung auswählen und auf die nächste Kreuzung ziehen, das Segment dazwischen verschwindet, solange keine Geometrie-Punkte darauf existieren. ===Brücken Funktion=== Diese Funktion ist ein wahrer Fehler-Indikator, denn wenn die Eigenschaften in den Segmenten nicht übereinstimmen, erscheint das Brückensymbol nicht. [[File:Strassen vereinen.png|left|350px]]Wähle ein Segment aus und mit der Taste für Mehrfachauswahl ('''Ctrl-Taste''' für Linux/Win und '''Command''' für Mac) das zweite Segment. Du kannst auch das Tastaturkürzel '''m''' verwenden. Ein Brückensymbol erscheint über der Kreuzung. <br> [[File:Vereinen Punkt entfernen.png|right]] Klicke auf das Symbol, die Straßen vereinen sich und die Kreuzung verschwindet. Die Segment-Ebene erhöht sich um eine Stufe höher als die des höchsten Segments. Ein Geometrie-Punkt erscheint an der Stelle, wo die Kreuzung war, dieser kann nach Bedarf entfernt werden. Wähle dazu das Segment aus und fahre mit der Maus auf den Punkt und lösche ihn mit '''d'''. Um mehr über die Brückenfunktion zu erfahren, lies die Seite [[Unterführungen_und_Brücken|Unterführungen und Brücken]] <br clear="all" /> ===Kreuzungen vereinen=== Diese Methode eliminiert das Segment zwischen den Kreuzungen. Sie ignoriert jegliche Eigenschaften der Segmente, die des mittleren Segments und die der Segmente auf beiden Seiten. Du solltest diese Methode auch nur dann verwenden, wenn Du sicher bist, dass es keinen reellen Grund für dieses Segment gibt. Das mittlere Segment darf keine Geometrie-Punkte aufweisen, es wird sonst ein scharfer Winkel kreiert, der in der Regel, in einem Speicherfehler endet. [[File:Strassen ziehen.png|left]][[File:Strassen ziehen2.png|right]]Wähle mit der Maus eine Kreuzung aus und ziehe sie auf die nächstgelegene Kreuzung. Es spielt dabei keine Rolle, von welcher Seite Du das Segment auf das andere vereinst. ''Anmerkung: Du musst die [[#Abbiegungen_bearbeiten|Abbiegungen]] der vereinten Segmente kontrollieren und ggf. nochmals bearbeiten''. ===Abbiegungen erlauben oder verbieten=== Um die Abbiegungen zu bearbeiten schaue weiter [[#Abbiegungen_bearbeiten|oben]] nach. ===Straßen von Kreuzungen abtrennen=== [[File:Kreuzung wegziehen.png|left]] [[File:Kreuzung weggezogen.png|right]]Dies ist eine einfache Angelegenheit, sofern Du die nötigen Rechte besitzt und das Segment nicht gesperrt ist. Markiere ein Segment und ziehe den Anfangs- oder Endpunkt (A in unserem Fall hier) des Segments von der Kreuzung weg. Nach dem Speichern bleibt die Kreuzung auf den Segmenten, von denen das einzelne Segment abgetrennt wurde übrig. Diese Kreuzung muss oder kann ggf. gelöscht werden. <br> [[File:Wegziehen von Endkreuzung.png|left]] [[File:Wegziehen von Endkreuzung2.png|right]] Zieht man eine Sackgasse von ihrer dazugehörigen End-Kreuzung weg, so wird die Kreuzung nach dem Speichern automatisch gelöscht, da sie ohne zugehöriges Segment auf der Karte nicht mehr verbleiben muss. Falls es sich um eine Sackgasse handelt, muss an das Ende wieder eine End-Kreuzung gesetzt werden. ===Sackgassen=== Um Sackgassen richtig zu bearbeiten schaue weiter [[#Kreuzung_am_Ende_einer_Sackgasse|oben]] nach. =Eigenschaften aktualisieren= Die Eigenschaften können für einzelne oder auch für mehrere Segmente gleichzeitig bearbeitet werden. Genau wie oben beschrieben für neue Segmente, können auch bei bereits bestehende Straßen die Eigenschaften den aktuellen Gegebenheiten angepasst werden. Klicke auf eines oder mehrere Segmente und aktualisiere die Straßen. [[File:Eigenschaften1.png‎]] Du kannst auch durch die Schaltfläche "Gesamte Straße auswählen" mehrere Segmente auswählen oder durch die Mehrfachauswahl mit der Taste '''m''' und auch durch halten der Ctrl-Taste. [[File:Eigenschaften2.png]] Sobald Du eines oder mehrere Segmente ausgewählt hast kannst Du sie im [[WME_Oberfläche_und_Steuerelemente#Reiter_wenn_Segmente_ausgew.C3.A4hlt_sind|Reiter Eigenschaften]] bearbeiten. [[Image:Eigenschaften3.png‎‎]] ==Adresse== Zuoberst im Reiter "Eigenschaften" kannst Du die richtige Adresse eingeben. Das Adressfeld beinhaltet Land, Stadt und Straße. Um Die Eigenschaften zu bearbeiten, klicke auf die Schaltfläche "Bearbeiten oder verwende das Tastaturkürzel '''e'''. Die Stadt und Straßennamen können verändert werden und beim Tippen eines Namens, erhältst Du eine Auswahl in der Dropdownliste. Stelle sicher, dass Du immer den richtigen Eintrag auswählst und keine unvollständigen Felder hinterlässt. Wenn Du keinen Orts-, oder Straßennamen vergeben willst, klicke auf "Ohne". Alle Segmente, die einen Namen haben musst Du durchgängig benennen. Segmente zwischen Straßen dürfen nicht leer bleiben. Wenn Du alle Eigenschaften eingegeben hast, klicke auf "Übernehmen". Wenn Du Eigenschaften nicht übernehmen willst, klicke auf "Abbrechen". Solange Segmente rot sind, erscheinen sie nicht in der App und sind auch nicht fürs Routing zu gebrauchen. Dies gilt für alle gezeichneten Segmente im Karteneditor und für Segmente, die mit der Waze-App aufgezeichnet wurden. Dies gehört zum Bestätigungsprozess in Waze, womit man eine Straße fürs Routing gültig macht. ===Alternative Straßennamen=== Die Alternativen Straßennamen sind nicht in der Waze-App sichtbar. Sie können jedoch für die Suche benutzt werden. Die Alternativen Namen können für jedes oder mehrere Segmente bearbeitet werden. Wenn eines der Segmente bei Mehrfachauswahl bereits einen Alternativen Namen besitzt, wird dieser sich nicht automatisch auf alle Segmente übertragen beim Speichern. Auch ist nicht ersichtlich, für welches Segment ein einzelner Alternativer Namen existiert. Du kannst Alternative Namen hinzufügen, wenn Du auf den Link "Alternative Namen hinzufügen" klickst. In der Regel hat der Alternative Stadtname den selben Eintrag wie das Hauptfeld "Stadt" in den Eigenschaften. Wird kein Stadtname benötigt, klicke auf "Ohne" [[File:AlternatverNameHinzufuegen.png]] Du kannst die Alternativen Namen auch bei Mehrfachauswahl aus den Segmenten löschen, klicke dazu auf das [[image:DeleteAltCB.png]]. ==Straßentyp== Den straßentyp wählst Du in der Dropdownliste aus.<br> [[File:Strassentyp.png]] Schau Dir die Kartenlegende für Dein Land an, um Informationen über die korrekte Klassifizierung der Straßen zu erhalten. ==Richtung== Die Fahrtrichtung einer Straße, wird mit dem entsprechenden Eintrag aus der Dropdownliste ausgewählt. [[File:Richtung.png‎]] Je nach dem, wie die Fahrtrichtung einer Straße verläuft, kannst Du auch hier eine Auswahl treffen. Du kannst hier auswählen, ob eine Straße als Einbahn entlang der [[#Vordefinierte_Richtung_der_Segmente|Erstellungs-Richtung]] des Segments von [[image:ACB.png]] nach [[image:BCB.png]] oder auch entgegengesetzt von [[image:BCB.png]] nach [[image:ACB.png]] verläuft. Und natürlich kannst Du auch eine Zweibahnstraße auswählen. Nachdem Du die Richtungs-Eigenschaften einer Straße gespeichert hast, siehst Du die Richtung anhand der blauen Pfeile auf den Segmenten. [[File:Einbahn.png]] Die Straßen auf der Basis-Karte sind mit der Richtung "Unbekannt" erstellt worden. Wenn die Straßen unbearbeitet sind, verändern sie ihre Richtung automatisch, wenn die Benutzer mit der Waze-App diese Straßen befahren. Wenn Du ein unbearbeitetes Gebiet der Basis-Karte bearbeitest, stelle sicher, dass die Richtungen der Einbahnstraßen korrekt sind. Alle Segmente, die bereits eine definierte Richtung haben, musst Du ebenfalls überprüfen. ==Ebene== [[File:Ebenen-definieren.png|right]] Die Ebene muss überall dort geändert werden, wo eine Straße über- oder unterführt. Standardmäßig ist die Ebene bei jeder Straße auf 0. Eine Brücke sollte demnach Ebene "1" besitzen, eine Unterführung Ebene "-1". Für mehr Informationen, besuche die Seite [[Unterführungen_und_Brücken|Unterführungen und Brücken]]. <br> <br> <br> <br> <br> <br> <br> <br> ==Sperren== [[File:Sperren.png|right]] Das Segment wird für Bearbeiter unter einer bestimmten Stufe gesperrt. Für Informationen zum "Sperren von Straßen" besuche diese [[Häufig_gestellte_Fragen#Was_ist_eine_gesperrte_Stra.C3.9Fe_im_Waze_Map-Editor.3F|Seite]]. Ein Editor kann hier eine Sperre von 1 bis zu seiner eigenen Stufe auswählen, ein Area-Manager mit Stufe 3 kann also z.B. eine Sperre von 1 bis 3 vergeben. Steht ein Segment auf Stufe 3, ist es für Bearbeiter mit Stufe 1 oder 2 gesperrt, Editoren mit Stufe 3 können es bearbeiten. '''Achtung:''' Wenn mehrere Segmente mit verschiedenen Stufen ausgewählt sind, wird das Feld die höchste vorkommende Stufe anzeigen. Verändert wird die Stufe aber nur, wenn man den Wert im Feld ändert und speichert. =Kreisverkehre= Die Seite [[Erstellen und bearbeiten eines Kreisverkehrs]] erklärt alles in Zusammenhang mit Kreisverkehren. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] bac365cab4bb39487be7403a168a574f6725f124 0 92 12019 2017-10-29T21:24:16Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Kreisverkehr Allgemein= Kreisverkehre behalten immer den höchsten Straßentyp bei. Wenn eine Stra…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Kreisverkehr Allgemein= Kreisverkehre behalten immer den höchsten Straßentyp bei. Wenn eine Straße mit den Typen Hauptstraße und Straße gezeichnet wird, so wird der Kreisverkehr auch als Hauptstraße angelegt. Das gleiche gilt Analog für alle Straßentypen außer Autobahn. Fängt eine Autobahn auf Stadtgebiet in einem Kreisverkehr an, so sollte der Kreisverkehr dem höchsten Straßentyp der nicht Autobahn ist zugewiesen werden: Hauptstraße, Bundesstraße, Landesstraße. Damit Routing-Fehler ausgeschlossen werden können, die in Zusammenhang mit Autobahn- Kreisverkehren entstehen können, sollten andere Straßentypen in Betracht gezogen werden. Kreisverkehre haben keine Straßennamen. Grund dafür ist die Schlechte Darstellung in der Waze-App. Kreisverkehre sollen jedoch einen Ortsnamen erhalten. Kreisverkehre erhalten auch keine Geschwindigkeitsbegrenzung, da man einen Kreisverkehr in der Regel ohnehin nur recht langsam durchfahren kann. Der Durchmesser des Kreisverkehrs ist auf 100 Meter beschränkt, um Vandalismus zu verhindern. =Was ist ein Kreisverkehr und was nicht?= Es gibt Fälle, wo '''kein''' Kreisverkehr gezeichnet werden soll. {| class="wikitable unsortable" border="1" |+ Dies sind keine Kreisverkehre |- ! Beschreibung ! Bild |- style="background:#FFFFFF; color:black" | Straßen kreuzen, aber in der Mitte befindet sich keine Insel, die ein Kreuzen durch die Mitte verhindert. Der Kreisverkehr ist nicht ausgeschildert oder nicht durch Markierungen auf dem Boden definiert. | [[Image:RdAbt-Not1.png|100px]] |- | Eine Straße, die in einer Sackgasse in einem Kreis endet, soll nicht mit einem Kreisverkehr am Ende erstellt werden. Ist die Straße groß genug, kann eine Schlaufe gezeichnet werden, aber keinen Kreisverkehr! | [[Image:Jct cul-de-sac island ex.png|100px]] |- |} <br> [[File:Schild-215.png|150x150px|thumbnail|right|Kreisverkehr: Auch ohne Schild möglich]] Für Deutschland gilt: Ein Kreisverkehr kann auch ohne Schild 215 (Kreisverkehr) gegeben sein. Schild 215 ist in Deutschland nicht an allen Kreisverkehren angebracht, sondern nur an denen wo auch die speziellen Vorfahrtregeln gelten sollen. Kreisverkehre die z.B. mit Ampel aufgebaut sind haben das Schild nicht. Vom Kreisverkehr abzusehen ist bei sehr großen Flächen (WME hat hier ein technisches Limit von 100m) und bei Kreuzungen in Wohngebieten, in denen mittig eine Schikane zur Entschleunigung aufgestellt ist. Im Falle von Unsicherheit (z.B. unregelmäßig geformte Kreuzungen oder exotische Verkehrsführung) wird die Hilfe eines Country Managers oder Bundeslandmanagers eingeholt. =Einen Kreisverkehr erstellen= Vielerorts entstehen Kreisverkehre aus Gründen des Verkehrsflusses, z.B häufigen Staus etc. Und wenn ein neuer Kreisverkehr gebaut wurde, müssen wir den natürlich auf die Karte bringen. Hier wird in ein paar Schritten erklärt, wie man einen Kreisverkehr im Karteneditor erstellt. Die Kreuzung an sich ist hier schon vorhanden, und es wird auch davon ausgegangen, dass sich die Karte im Hintergrund an der richtigen Stelle befindet. Ansonsten die GPS-Punkte beachten. Dazu die Ebene [[WME_Oberfläche_und_Steuerelemente#Auswahl_der_Ebenen|GPS-Punkte]] einblenden. [[Image:roundabout_01.png]] Die Situation hier ist sicherlich die einfachste, da alle Segmente bereits miteinander verbunden sind. [[Image:roundabout_02.png|320px|right]] Das erste was hier gemacht werden muss, ist die Kreuzung an die richtige Stelle in der Mitte des Kreisverkehrs zu verschieben. Dies ist einfach, wähle die Kreuzung aus und verschiebe sie in den Kreisverkehr im Hintergrund. <br clear="all" /> [[Image:roundabout_03.png|320px|right]] Sieht dann so aus: Im Laufe der Zeit wirst Du wohl verschiedene Varianten herausfinden Kreisverkehre zu erstellen und die damit verbundenen Segmente zu erstellen, löschen, verschieben etc. <br clear="all" /> [[Image:roundabout_05.png|320px|right]] Die südlichen Segmente werden hier im Beispiel von der Kreuzung getrennt, um damit die Straße im unteren Teil des Bildes zu erstellen. Das fehlende Segment ist neu einzuzeichnen und die Straße soll damit mit dem Kreisverkehr verbunden werden. <br clear="all" /> Da der Kreisverkehr hier mit vier Ein-/Ausfahrten bestückt ist, müssen wir noch das westliche [[Erstellen_und_bearbeiten_eines_Segments#Neue_Stra.C3.9Fe_einzeichnen|Segment]] hinzufügen. Diese ist hier zwar nur eine kleine Waldeinfahrt, aber sie sollte dennoch gezeichnet werden um korrekte Anweisungen auf der App zu erhalten. Denn der Fahrer, der da entlang fährt, wird diese Ausfahrt auch als Ausfahrt sehen. Wenn dies bis jetzt alles erledigt ist, kannst Du speichern wenn Du willst. [[Image:Kreisverkehr_hinzufügen.png‎|left]] Bewege den Mauszeiger über das grosse Straßenkurven-Icon auf der rechten Seite in der [[WME_Oberfläche_und_Steuerelemente#Hinzuf.C3.BCgen|Werkzeugleiste]] und wähle "'''Kreisverkehr'''" aus. Du kannst auch das [[WME_Schnellstart-Anleitung#Tastaturk.C3.BCrzel|Tastaturkürzel]] "'''o'''" verwenden. <br clear="all" /> [[Image:roundabout_06.png|320px|right]] Bewege den Mauszeiger in die Mitte des Kreisverkehrs, der Mauszeiger ist in diesem Modus ein Fadenkreuz. Klicke einmal und bewege die Maus von innen nach aussen. Ein oranger Kreis entsteht. Die Zahl in der Mitte bezeichnet dabei den Radius des Kreisverkehrs. '''Wenn Du einen ovalen Kreisverkehr erstellen willst, drücke und halte dazu die Shift-Taste.''' <br clear="all" /> [[Image:roundabout_07.png|320px|right]] Klicke ein zweites Mal, wenn Du mit Größe und Aussehen zufrieden bist. Der Karteneditor erstellt nun einen Kreisverkehr. Die neuen Segmente erscheinen in Orange, da sie noch nicht gespeichert wurden. Nach dem Speichern sind sie rot und als Einbahn in Fahrtrichtung definiert. Alle diese Segmente sind verbunden mit den Ein- und Ausfahrten und die Abbiegungen sind bereits als Soft-Turns erlaubt.<br> '''Bearbeite alle Kreuzungen des Kreisverkehrs mit "Q" und "W", um die Abbiegungen Hard zu machen.''' Lies dazu die Seite: [[Soft und Hard Turns]] <br clear="all" /> [[Image:roundabout_08.png|320px|right]] Gleich wie bei normalen Straßen, muss der Kreisverkehr zuerst [[Erstellen und bearbeiten eines Segments#Bestätigung durch Eingabe der Eigenschaften|bearbeitet]] werden, bevor er auf der App erscheint. '''In Waze verwendet man keinen Straßennamen für Kreisverkehre''', verwende dazu das Kontrollkästchen "Ohne". Wenn der Kreisverkehr einen eigenen Namen hat, zeichne einen [[WME_Schnellstart-Anleitung#Einen_Orientierungspunkt_erstellen|Orientierungspunkt]] in den Kreisverkehr hinein und benenne ihn mit dem Namen. <br clear="all" /> Wenn alles erledigt wurde und Du gespeichert hast, sieht es dann so aus, alle Straßen innerhalb des Kreisels werden gelöscht: [[Image:roundabout_09.png]] [http://www.youtube.com/watch?v=hOPjWKjGCio Hier gibt es ein Video dazu]. ==Sieht aus wie ein Kreisverkehr, ist aber keiner== Es kann sein, dass Du so einen Kreisverkehr antriffst. Ob er nun durch einen unwissenden Editor erstellt worden ist, oder vom Basis-Karten-Import stammt, diesen Kreisverkehr müssen wir nun korrigieren, da er nicht wie ein richtiger Kreisverkehr funktioniert. [[Image:replace_roundabout_01.png]] [[Image:replace_roundabout_02.png|320px|right]]Zuerst musst Du alle Segmente des vermeintlichen Kreisverkehrs löschen. <br clear="all" /> [[Image:replace_roundabout_03.png|320px|left]] Als nächstes musst Du alle Segmente, die in den neuen Kreisverkehr zeigen sollen etwas verlängern. <br clear="all" /> [[Image:replace_roundabout_04.png|320px|right]] Da der Kreisverkehr hier nicht auf der Karte ist, musst Du die [[WME_Oberfläche_und_Steuerelemente#Auswahl_der_Ebenen|GPS-Punkte]] dazu benutzen, um den Kreisverkehr an der richtigen Stelle zu positionieren. Im Beispiel sind genügend Punkte vorhanden, dies ist aber nicht immer so. Wähle wieder den Kreisverkehr aus in der Werkzeugleiste oder drücke die o-Taste. Positioniere das Fadenkreuz in der Mitte und zeichne den Kreisverkehr neu, indem Du den Radius nach außen vergrößerst. <br clear="all" /> Nachdem Du noch den Kreisverkehr korrekt bearbeitet und die Eigenschaften hinzugefügt hast, ist nach dem Speichern hier ein Kreisverkehr vorhanden, der auch in der Waze-App korrekte Anweisungen ausgibt: [[Image:replace_roundabout_07.png]] <br clear="all" /> =Bestehende Kreisverkehre bearbeiten= Manchmal muss man Kreisverkehre modifizieren, da vielleicht umgebaut wird oder Straßen gesperrt werden. Du kannst jederzeit die Kreisverkehre bearbeiten, wenn Du die nötigen [[Rechte zum Bearbeiten der Karte|Rechte]] dazu hast. ==Trennen und Verbinden von Straßen== Musst Du einzelne Segmente vom Kreisverkehr abtrennen oder darauf verbinden, lösche den Kreisverkehr und zeichne ihn neu! Probleme mit Kreuzungen, Abbiegungen und falschen Ansagen in der App können so von vornherein ausgeschlossen werden. ==Segmente des Kreisverkehrs löschen== Beim löschen von Kreissegmenten musst Du folgendes beachten: * Du kannst nur alle Segmente des Kreisverkehrs löschen damit Du speichern kannst. Ansonsten erscheint diese Fehlermeldung: <br>''Der markierte Kreisverkehr bildet keinen Kreis. Bitte korrigieren und erneut versuchen.'' [[Image:Kreisverkehr_segment_löschen.png|700px]] <br> * Wenn Du mit Mehrfach-Auswahl alle Kreissegmente auswählst, musst Du zuerst dieses Popup mit "Ok" bestätigen: <br> ''You are about to delete multiple segments, are you sure?'' * Danach kannst du speichern. [[Image:Kreisverkehr_segment_löschen_fehler.png]] <br> =Straßentypen im Kreisverkehr= Es gibt Situationen, wo mehrere Straßentypen (Straße, Hauptstraße, Landesstraße, etc.) im Kreisverkehr aufeinander treffen. Um ein effizientes Routing zu erzielen, musst Du darauf achten, welche Straßentypen Du definierst. Ziel davon ist: * Unnötige [[Wie_Waze_Routen_kalkuliert#Penalty_System|Penalties]] zwischen den verbundenen Straßen zu vermeiden oder zu minimieren. * Einen Kreisverkehr fürs Routing nicht zu "attraktiv" zu machen, wo dies nicht unbedingt nötig ist. Da ein Kreisverkehr '''nicht''' auf Autobahnen existiert, ignorieren wir die Freeway Segmente auf dieser Seite. Die Straßentypen, die uns interessieren sind der Reihe nach, vom höchsten bis zum tiefsten Typ: Bundesstraße, Landesstraße, Hauptstraße, Straße. Wir betrachten Zufahrtsstraße, Privatstraße und Parkplatz gleich, wie eine normale Straße. Um zu ermitteln, welchen Straßentyp wir für einen Kreisverkehr verwenden: # Identifiziere die zwei Segmente mit dem höchsten Straßentyp. ## Wenn eine Straße in zwei Einbahnstraßen-Segmente aufgeteilt ist, zähle die beiden Einbahnstraßen als ein einzelnes Segment. ## Die beiden verbundenen Segmente mit den höchsten Typen können gleich oder unterschiedlich sein. ## Wenn eine Rampe mit dem Kreisverkehr verbunden ist, verwende den Typ, auf den sich die Rampe verbindet. # Wähle den tiefsten Typ der zwei Segmente. <br> {| class="wikitable unsortable" border="1" |+ Leitfaden für Straßentypen bei Kreisverkehren |- ! Beschreibung ! Top 2<br>'''''(KV Typ)''''' ! Bild |- style="background:#FFFFFF; color:black" | Straße und Hauptstraße kreuzen im Kreisverkehr, wir haben hier zwei Straßen-Segmente und zwei Hauptstraßen-Segmente. | Hauptstraße, '''''Hauptstraße''''' | [[Image:RdAbt_PrPr.png|100px]] |- | Drei Straßen-Segmente und ein Hauptstraßen-Segment. | Hauptstraße, '''''Straße''''' | [[Image:RdAbt_PrSt.png|100px]] |- | Ein Straßen-Segment und drei Hauptstraßen-Segmente. | Hauptstraße, '''''Hauptstraße''''' | [[Image:RdAbt_PrPr3.png|100px]] |- | Landesstraße und Bundesstraße, je zwei Segmente. | Bundesstraße, '''''Bundesstraße''''' | [[Image:RdAbt_MjMj.png|100px]] |- | Ein Landesstraßen-Segment und drei Bundesstraßen-Segmente. | Bundesstraße, '''''Bundesstraße''''' | [[Image:RdAbt_MjMj3.png|100px]] |- | Eine Bundesstraße, zwei Hauptstraßen-Segmente und ein Straßen-Segment. (Bundesstraße beginnt oder endet am Kreisverkehr.) | Bundesstraße, '''''Hauptstraße''''' | [[Image:RdAbt_MjPr.png|100px]] |- | Bundesstraße, Landesstraße, und zwei Hauptstraßen-Segmente. (Wenn Hauptstraße gewählt wird, entsteht ein Penalty von der Landesstraße zur Bundesstraße.) | Bundesstraße, '''''Minor Highway''''' | [[Image:RdAbt_MjMn.png|100px]] |- | Zwei Straßen-Segmente, ein Hauptstraßen-Segment und ein Bundesstraßen-Segment. | Bundesstraße, '''''Hauptstraße''''' | [[Image:RdAbt_MjPr2.png|100px]] |- |} <br> ==Segmente für Ein- und Ausfahrten in Kreisverkehre== [[Image:RdAbt-NoDivRd.png|150px|right]] Die Straßen-Segmente, die in und aus einem Kreisverkehr führen, werden allgemein als einfache Straßen verbunden, rechtwinklig (90 Grad) am Kreisverkehr. Dies macht es einfacher für den Benutzer, die Karte in die Realität umzusetzen und nur die Ein- und Ausfahrten zu visualisieren. Die Waze-App wird dem Fahrer sagen, '''"nehmen Sie die zweite Ausfahrt"''', so weis der Fahrer, wie weit weg das ist im Kreisverkehr, ausgehend von dem Punkt, wo er sich gerade befindet. In Fällen, wo die Ein- und Ausfahrten in Kreisverkehre '''sehr''' weit auseinander liegen, macht es Sinn diese in zwei Einbahn-Segmente aufzuteilen. Als weitere Hilfe dient diese [[Base Map 1.0|Seite]]. <br> =Navigationsanweisungen verstehen= * Was ist ein normaler Kreisverkehr? * Warum wird "rechts abbiegen" / "geradeaus" angesagt? * Warum wird "nehmen Sie die X Ausfahrt" angesagt? <br> Bei einem normalen Kreisverkehr erhält man die Ansage "rechts / links abbiegen" oder "geradeaus fahren". Ist es kein normaler Kreisverkehr, wird "nehmen Sie die X Ausfahrt" angesagt. <br> Was ist ein normaler Kreisverkehr? Ein Kreisverkehr mit 4 Kreuzungen und einem Mittelpunkt. Alle Kreuzungen sind innerhalb eines normalen Bereichs (90° +/- 30° und 180° +/- 30°) vom Eintrittspunkt her ausgerichtet, wenn man sich eine XY-Achse vorstellt, die vom Eintrittspunkt her durch den Mittelpunkt führt. Das bedeutet: Der gleiche Kreisverkehr kann als "normal" gelten, wenn man von einer Kreuzung her in den Kreisverkehr einfährt, und als "nicht normal", wenn man von einer anderen Kreuzung her in den Kreisverkehr einfährt. Hier einige Beispiele dazu. <br> Der Einfachheit halber, betrachten wir einen Kreisverkehr mit drei Ausfahrten. <br> [[Image:Roundabout_1.jpg]]<br> Jedes Mal, wenn man sich diesem Kreisverkehr nähert (von einer der drei Kreuzungen her) wird eine imaginäre Linie vom Eingang her durch den Mittelpunkt gezogen.<br> Der Winkel der Segmente zu einem der drei Kreuzungen auf dem Kreisverkehr, spielt dabei keine Rolle. Es könnte entweder einer in den beiden Beispielen hier sein, oder einen Winkel irgendwo dazwischen.<br> [[Image:Roundabout_2.jpg]] <br> [[Image:Roundabout_3.jpg]] <br> '''Wir kommen von Kreuzung Nr. 1 her:'''<br> [[Image:Roundabout_4.jpg]] <br> Beide Ausfahrten, 2 und 3 sind hier innerhalb des Normalbereichs (90° +/- 30° und 180° +/- 30°). Hier wird in beiden Fällen "rechts abbiegen" oder "geradeaus fahren" angesagt. <br/><br/> '''Wir kommen von Kreuzung Nr. 3 her:''' <br/> [[Image:Roundabout_5.jpg]] <br/> Beide Ausfahrten, 1 und 2 sind nicht innerhalb des Normalbereichs - In beiden Fällen wird nun "nehmen Sie die X Ausfahrt" angesagt.<br> Hinweis: Selbst wenn einer dieser Ausfahrten im Normalbereich liegt, der Kreisverkehr selbst gilt als "nicht normal" und alle Ausfahrten werden mit "nehmen Sie die X Ausfahrt" angesagt. Der gesamte Kreisverkehr muss "normal" sein. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 89c5b4d90307062326b3ee136f6de2eeb29717bd 0 93 12020 2017-10-29T21:24:47Z Popel22 24 Die Seite wurde neu angelegt: «Orte (engl: "''Places''") sind die POIs (Points of Interest bzw Punkte von Interesse) von Waze. Es werden zwei verschiedene Arten von POIs unterstützt. '''Punk…» wikitext text/x-wiki Orte (engl: "''Places''") sind die POIs (Points of Interest bzw Punkte von Interesse) von Waze. Es werden zwei verschiedene Arten von POIs unterstützt. '''Punkt Orte''' werden als Punkt im WME dargestellt und der APP nur zur Suche zur Verfügung gestellt. Punkt Orte, auch '''Navigationspunkt''' genannt, werden in der APP nicht dargestellt. Wann ein Punkt genutzt werden soll findet ihr in der [[#Wann_ist_eine_Fl.C3.A4che_zu_verwenden.2C_wann_ein_Punkt.3F|Tabelle]]. '''Flächen Orte''' werden als Fläche in WME sowie in der APP dargestellt. Flächen Orte, auch '''Orientierungspunkte''' genannt, werden erst ab einer gewissen Größe in der APP dargestellt. Darum ist nicht jeder zB. Bankomat als Fläche einzuzeichnen, da dieser nicht angezeigt wird. Orientierungspunkte dienen wie der Name schon sagt als Orientierung. Auch hier wieder: Wann eine Fläche genutzt werden soll findet ihr in der [[#Wann_ist_eine_Fl.C3.A4che_zu_verwenden.2C_wann_ein_Punkt.3F|Tabelle]]. <br /> ==Navigationspunkt== Die Punkte werden wie folgt dargestellt: {{clear}} [[File:wme_place.png]] Standard Punkt {{clear}} [[File:wme_place_selected.png]] Ausgewählter Punkt {{clear}} [[File:wme_place_changed.png]] Punkt mit nicht abgespeicherten Änderungen {{clear}} [[File:wme_place_pending_update.png]] Punkt mit ausstehenden Updates {{clear}} '''Navigationspunkte Details''' *Der Navigationspunkt sollte auf oder in der Nähe des Segmentes liegen, zu dem der Fahrer navigiert werden soll. <u>Der Punkt ist der Endpunkt der Navigation</u>. Details siehe unten. ==Orientierungspunkt== Die Fläche wird als Polygon dargestellt und kann genauso wie Straßensegmente über die Nodes bearbeitet werden. Die Flächen werden im WME pink angezeigt, wenn sie ausgewählt werden dann werden sie türkis angezeigt. {{clear}} [[File:Wme gas station area.png]][[File:Wme gas station area selected.png]] {{clear}} '''Orientierungspunkte Details''' *Orientierungspunkte haben ein Fadenkreuz (blau/weiß) für den Navigationsendpunkt *Das Fadenkreuz kann innerhalb der Fläche bzw ein kleines Stück außerhalb der Fläche platziert werden *Das Fadenkreuz sollte - genau wie die Navigationspunkte - dort platziert werden, wo die Navigation enden soll. ===Größe der Orientierungspunkte=== Manche ''Orte'', die als Orientierungspunkte zu qualifizieren sind, können mehrere Gebäude, Straßen, Freiflächen, Parkplätzen etc, enthalten. Hier sollte man nur einen Orientierungspunkt für das ganze Gelände entlang der Grundgrenze (z.B. ein Krankenhausgelände) anlegen. Damit ist gewährleistet, dass im Client die Fläche auch in kleinen Zoomstufen korrekt dargestellt und bezeichnet wird. In anderen Fällen kann ein Orientierungspunkt für ein ganzes Gebäude einzeichnet werden, wenn die Grundgrenzen mit dem Gebäude deckungsgleich sind, um die Gesamtgröße des POI darzustellen. === Übereinanderlegen von Orientierungspunkten === In manchen Fällen kann sich ein ausgedehnter Orientierungspunkt über andere POIs erstrecken, die selbst als Orientierungspunkte einzutragen wären, beispielsweise verschiedene Stationen innerhalb eines Krankenhausgeländes oder einzelne Geschäfte in einem Einkaufszentrum. Derzeit kann der Waze Client (Waze App und Livemap) Orientierungspunkte innerhalb eines Orientierungspunktes nicht gesondert darstellen, sondern zeigt nur deren Namen an, nicht jedoch ihren räumlichen Umfang. Der Nutzer kann daher derzeit nicht unterscheiden, wo innerhalb der großen Fläche die "Unterflächen" liegen. Zukünftige Versionen des Waze Client könnten übereinanderliegende Flächen möglicherweise sinnvoller darstellen, im Hinblick darauf können entsprechende Orientierungspunkte in einem großen Orientierungspunkt bereits eingezeichnet werden. '''Empfehlenswert ist derzeit jedoch, Navigationspunkte für die Bestandteile einer großen Fläche zu verwenden''', außer wenn es unbedingt notwendig ist, dass die Namen der Orientierungspunkte in einer Fläche jetzt im Client sichtbar sind. Sobald eine korrekte Darstellung im Client gewährleistet ist, können die jetzt eingezeichneten Navigationspunkte ja jederzeit in Orientierungspunkte umgewandelt werden. == Darstellung von ''Orten'' im Client == Die meisten ''Orte'' werden im Client und [[Live map]] als schattierte Flächen dargestellt. Extrem kleine Orientierungspunkte werden überhaupt nicht dargestellt, auch nicht in der größten Zoomstufe. Navigationspunkte werden im Client und [[Live map]] nicht dargestellt, nach ihnen kann aber in der Waze App gesucht werden. Ein Suchtreffer eines Waze ''Ortes'' sollte vorrangig vor anderen dargestellt werden, auch in der automatischen Suchvervollständigung. == Richtiges Setzen eines Punkts für einen ''Ort'' == === Platzieren eines Navigationspunktes === [[File:wme_point_place_at_front_door.png|thumb|Navigationspunkt beim Haupteingang eines Geschäfts.]] Der Navigationspunkt soll auf oder so nahe wie möglich bei dem Straßensegment platziert werden, zu dem der User geroutet werden soll. Der Waze Routingserver wird den User zu dem Element routen, das der Position des Punktes am nächsten liegt. <u>Der Navigationspunkt wird als Endpunkt der Route verwendet</u>. Ist der POI beispielsweise innerhalb eines Gebäudes, so soll der Punkt bei oder nahe dem Haupteingang des Gebäudes platziert werden. Überlege immer, wo ein Auto zufahren würde, das dort jemanden hinbringen möchte! ==== Einen Navigationspunkt verschieben ==== Um einen Navigationspunkt zu verschieben, klicke zuerst auf das Symbol des Navigationspunktes, das daraufhin zu einem [[File:wme_venue_selected.png]] wird. Jetzt kannst du noch einmal draufklicken und den Punkt wie gewünscht verschieben. ==== Beispiele für die Platzierung eines Navigationspunktes ==== * Ein Gebäude mit einem Navigationspunkt: ** Wenn es nur einen einzigen Eingang gibt, platziere ihn bei dieser Türe. ** Wenn es mehrere Eingänge auf derselben Gebäudeseite gibt (wie zB bei einem großen Supermarkt), platziere ihn in gleicher Entfernung und auf einer Linie mit den Eingängen. ** Wenn es mehrere Eingänge auf verschiedenen Seiten gibt (wie zB bei einem Einkaufszentrum), platziere ihn, wenn es keinen "eindeutigen" Haupteingang gibt ("Haupteingangsregel"), bei dem Eingang, der beim größten Parkplatz liegt, sonst bei dem Eingang von der Straße aus, aus der sich die Postanschrift des Geschäfts ergibt. * Ein Gebäude, das mehrere Navigationspunkte enthält: ** Bei einer Einkaufszeile (''strip mall'', mehrere Geschäfte im Freien nebeneinander) gilt wie oben die "Haupteingangsregel". ** Bei einem größeren Einkaufszentrum platziere die Punkte so nahe wie möglich an die tatsächlichen Positionen der einzelnen Geschäfte. So weiß einerseits der User, wo er genau hin muss, andererseits kann der Routingserver den Parkplatz auswählen, der dem Geschäft am nächsten liegt. ''{{u|Achtung:}} diese Regel soll nur soweit angewendet werden, als der Punkt damit nicht einem Straßensegment am nächsten liegt, von dem eine Zufahrt/ein Zugang zum Einkaufszentrum nicht möglich ist. Wenn durch diese Regel beispielsweise ein Punkt am nächsten zu einer Straße auf der Rückseite des Gebäudes liegen würde, das nicht zum Parkplatz des Einkaufszentrums gehört, so ist die "Haupteingangsregel" anzuwenden. sonst würden die User auf die Rückseite des Gebäudes geroutet werden, wo sie keine Zugangsmöglichkeit zum Einkaufszentrum (und dem Punkt darin) haben.'' ** Bei Bürogebäuden muss man aus demselben Grund aufpassen. Hier gilt sinngemäß das gleiche wie bei den vorherigen Beispielen, der Navigationspunkt ist dort zu setzen, wo der Eingang zu allen Büros ist bzw. wo ein Auto zufahren würde. {{clear}} === Platzieren eines Orientierungspunktes === Das [[File:wme_place_stop_point.png]] Icon ist der Navigationsendpunkt für Orientierungspunkte. Hier sieht man ein Beispiel für eine Orientierungspunkt (hier ein großer Park), der eine Einfahrtstraße auf der Ostseite hat. Das zweite Bild zeigt im Detail, wie bei diesem Typ von Orientierungspunkt der Navigationsendpunkt zu setzen ist. {{clear}} [[File:Wme park place large.png|thumb|left|300px|WME Orientierungspunkt]] [[File:Wme park place zoom target.png|thumb|right|300px|WME Orientierungspunkt vergrößert]] {{clear}} ==== Maximale Entfernung des Navigationsendpunktes vom Orientierungspunkt ==== Wenn man einen Navigationsendpunkt verschiebt, kann er maximal innerhalb des schwarzen Rahmens vom Orientierungspunkt wegverschoben werden. {{clear}} [[File:wme_place_area_stop_point_boundary.png|center]] {{clear}} {{Red|Wenn man einen Orientierungspunkt verschiebt und der Navigationsendpunkt dadurch außerhalb des schwarzen Rahmens zu liegen kommt, erhält man beim Speichern eine Fehlermeldung. Dann muss man den Navigationsendpunkt wieder innerhalb des schwarzen Rahmens verschieben, erst dann ist das Speichern wieder möglich.}} ==== Verschieben eines Orentierungspunktes ==== Man kann eine Fläche als Ganzes verschieben, indem man sie durch Anklicken auswählt und dann das Verschiebesymbol [[File:wme_place_drag_handle.png]] anklickt, verschiebt und an der gewünschten Position wieder auslässt. {| class="wikitable unsortable" style="background:#FFFCB0; font-size:100%; margin: 1em auto 1em auto" border="1" |- ! '''{{Red|ACHTUNG:}}''' |- | Wenn man einen Orientierungspunkt irrtümlich verschoben hat, kann man das ganz leicht durch Drücken von Strg + Z rückgängig machen. |- |} {{clear}} == ''Orte'' Detailinformationen == Jeder ''Ort'', egal ob Punkt oder Fläche, sollte so viele Detailinformationen wie möglich enthalten (Name, Kategorieeinteilung, Adresse mit Hausnummer, Land). Wenn es wirklich keinen Straßennamen oder keine passende Stadtbezeichnung gibt, dann ist das Kästchen "Ohne" anzuklicken. Insbesondere das Ergänzen der Adresse und Hausnummer ist wesentlich, da diese bei den Suchtreffern angezeigt wird und so gleichartige Treffer unterscheidbar macht (zB SPAR als Bezeichnung, Adresse und Hausnummer zur Unterscheidung von anderen SPAR in der Nähe). === Tab Allgemein === Der Tab Allgemein enthält die Grundinformationen allgemeiner Natur: Kategorien, Name, Beschreibung, bei Tankstellen die Marke, Private Wohnstätte (''Residential private'') / öffentlicher Ort (''public''), Öffnungszeiten, Land, Stadt, Straße und Hausnummer. ==== Benennung ==== Um eine Einheitliche Benennung gewährleisten zu können, sollte man sich auf der Website des jeweiligen POIs informieren, wie er geschrieben gehört. Bei Ketten von Unternehmen gehört "GmbH" (und Süd bzw. Nord bei ALDI) nicht in die Bezeichnung. Wenn mehrere Niederlassungen in einer Stadt/Gemeinde sind, sodass die Stadt aus der Adresse nicht unterscheidungskräftig ist, ist der Stadtteil bzw. ein unterscheidungskräftiger Zusatz beim Namen einzutragen. Ansonsten ist die Stadt nur in der Adresse einzutragen, diese wird beim Suchtreffer ohnehin angzeigt. In Zukunft wird auch die Adresse (Stadt und Straße/Hausnummer) beim Suchtreffer angezeigt, ein Zusatz beim Namen zur Unterscheidung ist daher nicht notwendig. Einige Beispiele dazu (diese Übersicht bei Bedarf einfach ergänzen, damit möglichst Einheitlichkeit gewährleistet ist): * ADEG * ALDI * A.T.U Auto-Teile-Unger * BAUHAUS * bauMax * bft * BILLA * BIPA * dm drogerie markt * EUROSPAR * Esso * Hofer * INTERSPAR * kika * Lidl * Maximarkt * McDonald's * Media Markt * Merkur Markt * Mömax * MPREIS * Netto Marken-Discount * NORMA * OBI * PENNY * Postfiliale und BAWAG P.S.K. 5026 * REWE * Rossmann * Shell * SPAR * TAKKO FASHION * Tesla Supercharger ''Ortsname'' * Unimarkt * XXXLutz * Zielpunkt * ZGONC * ... '''Bahnstationen / Haltestellen''' Bei U-Bahn Stationen sollte man ein "U" vor den Stationsnamen setzen. Aus dem einfachen Grund weil in der Suche nicht hervorgeht ob es sich nun um eine U-Bahn Station, einen naheliegenden (gleich benannten) Ort oder um eine gleichnamige Straße handelt. Das gleiche gilt für Bus und Straßenbahn Stationen. Vor diese allerdings ein "H" setzen. In beiden Fällen ist es hilfreich, auch alle Linien die von dieser Station wegfahren in der Beschreibung einzutragen. Da es keine eigene Kategorie gibt für Straßenbahnen wird in diesem Fall Bahnhof genommen. ==== Beschreibung ==== '''{{Red|Eines vorweg:}}''' {{Red|Verwende nicht das Feld "Beschreibung" für Notizen an andere Editoren.}}<br>Dieses Feld ist in der Waze App sichtbar und sollte nur Informationen enthalten, die tatsächlich den ''Ort'' betreffen.<br> Dazu kann man sich auch von der jeweiligen HP inspirieren lassen, um den Ort mit ein zwei Sätzen kurz zu charakterisieren.<br> Für "Sehenswürdigkeit / Historische Stätte" (Tourist Attraction / Historic Site) sollte dieser Hinweis, als spezielles Service für nichtdeutschsprachige Besucher, zusätzlich auf englisch eingetragen werden (die jeweilige HP hilft auch hier schnell einen passenden Satz zu finden), da diese Kategorie erwartungsgemäß besonders von Touristen aufgerufen wird. Hier sind zwei Beispiele für einen Orientierungspunkt einer Tankstelle und eines Casinos mit den ausgefüllten Informationen: {{clear}} [[File:wme_tankstelle_general.png|border||Ort Details]][[File:wme_place_casino_general_de.png|border||Ort Details]] {{clear}} === Tab Weitere Infos ''(More Info tab)'' === Der Tab ''Weitere Infos'' Enthält zusätzliche nützliche Informationen zum ''Ort''. Hier kann man die Telefonnummer eintragen, die Website-Adresse sowie andere Dienste/Services. {{clear}} [[File:wme_place_more_info_de.png|border|right|Weitere Infos]] ==== Website ==== ===== Tankstellen ===== Bei Tankstellen in Österreich ist als Website ein Link nach folgendem Muster anzuführen. http://www.oeamtc.at/spritapp/ShowGasStation.do?spritaction=show&gsid=1208475 <br>Damit erreichen wir einheitliche, umfangreiche und tagesaktuelle Informationen über die Tankstellen, die damit verlinkte Seite bietet auch noch weitere Vorteile bei der Suche nach dem günstigsten Ort seinen Tank zu füllen.<br> Tipp: damit findet man auch die "gsid" anderer Tankstellen heraus, damit man dann dort den richtigen Link eintragen kann. ==== Telefon ==== Um eine Einheitlichkeit zu gewährleisten, werden Nummern folgendermaßen geschrieben: '''Internationale Verkehrsausscheidungsziffer (Ländercode) + Vorwahl (ohne die führende Null) + Telefonnummer''' Sieht dann wie folgt aus * Wiener Nummer: +43 1 123456789 * Grazer Nummer: +43 316 123456789 * Innsbrucker Nummer: +43 512 12346789 usw... ==== Dienste/Services ''(Services)'' ==== Die eingetragenen Dienste sollen dem User helfen sich zu entscheiden, zu welchem ''Ort'' er fahren soll, wenn mehrere zur Auswahl stehen. Bei jeder Art von ''Ort'' stehen dieselben Felder zur Auswahl. Die Checkboxen haben nur zwei Zustände, entweder 'ja' oder 'nein / nicht ausgewählt'. Ein User kann daher nicht unterscheiden, ob ein Dienst nicht existiert, also 'nein' gemeint ist, oder von einem Editor einfach noch nichts ausgewählt wurde. Dass er sich auf die ''ja'' verlassen kann, sollte im Normalfall ausreichen. Hier sind die einzelnen Services, die ausgewählt werden können: ===== Parkservice / Valet Service (''Valet service'') ===== Der ''Ort'' hat ein Parkservice [http://de.wikipedia.org/wiki/Valet_parking valet parking], bei dem man das Auto einem dort Angestellten übergeben kann, um es parken. Dieses Angebot kann kostenlos oder kostenpflichtig sein. ===== Drive-In (''Drive-through'') ===== Der ''Ort'' hat einen [http://de.wikipedia.org/wiki/Drive-in drive-in]-Schalter (ursprüngliche Bezeichnung im Englischen ''drive-thru''), bei dem Essen abgeholt oder Geschäfte getätigt werden können, ohne das Auto zu verlassen; kommt vor bei (insbesondere Fast-Food) Restaurants, Banken oder Apotheken. ===== WLAN Hotspot (''Wi-Fi'') ===== Der ''Ort'' bietet seinen Kunden '''kostenloses''' [http://de.wikipedia.org/wiki/Wireless_Local_Area_Network Wi-Fi / einen WLAN Hotspot] an. Das WLAN kann komplett frei verfügbar oder mit einem beim Betreiber des ''Orts'' erhältlichen Zugangscode benutzbar sein. ===== Toilette (''Restrooms'') ===== Der ''Ort'' hat eine Toilette, die von Kunden benutzt werden kann. ===== Kreditkarten werden akzeptiert (''Accepts credit cards'') ===== Der ''Ort'' akzeptiert Kreditkarten zur Bezahlung von Waren und Dienstleistungen. Zwischen verschiedenen Arten von Kreditkarten wird dabei nicht unterschieden. ===== Reservierungen möglich (''Reservations'') ===== Der ''Ort'' akzeptiert Reservierungen, zB. eine Reservierung für ein Abendessen zu einer bestimmten Zeit. ===== Plätze im Freien (''Outdoor seating'') ===== Der ''Ort'' bietet Plätze im Freien an, um dort zB zu essen und zu trinken. Diese Plätze können sich auf der Straße, am Gehsteig, in einer Fußgängerzone, in einem umzäunten Bereich oder sonstwo auf einem Privatgrundstück befinden. ===== Klimaanlage (''Air conditioning'') ===== Der ''Ort'' besitzt eine Klimaanlage, um die Luft zu kühlen und zu entfeuchten. ''Tip:'' auf eine Klimaanlage lässt sich auch schließen, wenn man entsprechende Einrichtungen auf dem Dach oder auf der Gebäudeseite in Luftfotos oder auf den beim ''Ort'' verknüpften Fotos sieht. ===== Kundenparkplatz (''Parking for customers'') ===== Der ''Ort'' hat einen Kundenparkplatz, dieser kann kostenlos oder kostenpflichtig sein. ===== Zustellungen (''Deliveries'') ===== Der ''Ort''-Betreiber stellt seine Produkte an den Kunden (innerhalb eines gewissen nicht allgemein festgelegten Bereiches) zu. ===== Zum Mitnehmen (''Take Away'') ===== Man kann das Produkt vom ''Ort'' mitnehmen. ===== Rollstuhlgerecht (''Wheelchair accessible'') ===== === Tab Fotos ''Photos tab'' === Alle Fotos, die User mit einem ''Ort'' verknüpft haben, sind in diesem Tab sichtbar. Im WME können Fotos derzeit nur geprüft und gelöscht werden, hinzufügen kann man sie nur in der Waze App. Klicke auf ein Foto, um es zu vergrößern. {{clear}} [[File:wme_place_photos.png|border|center|Ort / Fotos]] {{clear}} ==== Bestimmen von akzeptierbaren Fotos ==== Es ist schwierig, generell zu sagen, welche Fotos akzeptierbar sind. Das hängt auch wesentlich von der Art des ''Orts'' ab. Allgemein gesagt sollen nur solche Fotos akzeptiert werden, die dem Fahrer helfen, bei der Anfahrt zu klären, was genau sein gewünschtes Ziel ist. Das System versucht auch, dem User das passendste Foto in Bezug auf seine Anfahrtsrichtung, die Tageszeit etc. zeigen. An folgenden Richtlinien sollen sich sowohl Editoren als auch User orientieren, wenn sie Fotos machen/bestätigen: '''Fotos sollen:''' *Eine Außenansicht des ''Orts'' zeigen *eine gute Qualtität und Erkennbarkeit haben (nicht unscharf/verschwommen, nicht durch regennasse oder schmutzige Scheiben, nicht aus einem fahrenden Auto/Zug etc) *korrekt belichtet sein *dazu geeignet sein, den angepeilten ''Ort'' von daneben liegenden Gebäuden zu unterscheiden '''Fotos können beispielsweise das Folgende zeigen:''' *Eingang eines Geschäfts *Vorderseite des Hauses / Haupteingang mit Geschäftsbezeichnungen *Eine schräge Ansicht der Front und der Seite, um das richtige Gebäude eindeutig zu bezeichnen. *Blick von der Straße mit Werbetafeln *Bilder bei Tageslicht *Bilder bei Abend oder Nacht, solange auf dem Bild etwas erkennbar ist und es zur Identifizierung des ''Orts'' nützt '''Fotos dürfen <u>nicht</u>:''' *{{Red|Personen so ablichten, dass sie erkennbar sind (insbesondere keine erkennbaren Gesichter).}} *{{Red|lesbare Autokennzeichen zeigen.}} *irgendetwas anderes zeigen, das es erlaubt, eine bestimmte Person dem Foto/dem Ort zuzuordnen *Fotos von Privatgebäuden dürfen nur von der öffentlichen Fläche (Straße/Gehsteig) gemacht werden, nicht z.B. in der Einfahrt stehend. Beispiele für geeignete Fotos: [[Image:Einkaufszentrum.jpg|Straßenansicht eines Einkaufszentrums zum Auffinden]] [[Image:Baeckerei.jpg|Bäckerei - Straßenansicht]] '''Nicht geeignet''' sind Innenansichten oder Bilder, auf denen Personen deutlich zu erkennen sind: [[Image:Schwimmbad.jpg|Hier ist eine Person im Vordergrund deutlich zu erkennen.]] [[Image:MCDonalds.jpg|McDonald's von innen hilft nicht bei der Navigation]] ==== Ein Foto bei einem ''Ort'' löschen ==== {{Red|Überlege immer gut, bevor du ein Foto löschst! Ein einmal gelöschtes Foto kann nicht wiederhergestellt werden. Lösche ein Foto nur, wenn es wirklich nutzlos ist, wenn überhaupt nichts zu erkennen ist oder wenn es anstößig, unpassend, gegen den guten Geschmack (engl.: ''inappropriate'') ist. Ansonsten ist ein nicht ganz optimales Foto oft besser als gar keines, jedes Foto kann ja später gelöscht werden, wenn andere, bessere Fotos hinzugefügt wurden.}} [[File:wme_place_photo_hover.png|right]] Alle ungeeigneten oder dem guten Geschmack widersprechenden Fotos sollen gelöscht werden. Fahre dazu mit der Maus im Tab ''Fotos'' über das Foto und klicke auf das X, das im oberen rechten Eck des Fotos erscheint. == Ort-Aktualisierungen ''Place Updates'' (Moderation) == [[File:wme_placemarker_new.png]][[File:wme_placemarker_new_photo.png]][[File:wme_placemarker_updated_details.png]][[File:wme_place_update_marker_multiple.png]] Der Layer "Ort-Aktualisierungen" (engl: ''Place updates'') zeigt Orte an, zu denen Updates vorliegen. Wenn ein [[#Was_ist_ein_vertrauensw.C3.BCrdiger_User.2FEditor.3F|nicht vertrauenswürdiger User]] ein Foto oder einen ''Ort'' hinzufügt, erhalten diese einen entsprechenden Status für die Moderation. Das oben dargestellte Update Icon zeigt an, dass an dieser Stelle auf der Karte eine Moderation notwendig ist, genau wie bei einem Update Request oder einem Map Problem. {{clear}} [[File:wme_place_area_with_update.png|right|thumb|Orientierungspunkt Update Icon]] *Das ''Ort'' Update Icon ist nur zu sehen, wenn der Layer "Ort-Aktualisierungen" aktiviert ist. *Wenn bei Navigationspunkten Updates anstehen, sind diese mit dem [[File:wme_place_pending_update.png]] Icon auch zu sehen, wenn der Layer "Ort-Aktualisierungen" deaktiviert ist. *Ein Orientierungspunkt wird mit dem oben dargestellten Icon in der Mitte der Fläche dargestellt. {{clear}} [[File:wme_place_update_new_place.png|right|thumb|Neuer ''Ort'']] Wenn man auf das ''Ort'' Update Icon klickt, kommt man zu einer Maske mit allen Informationen des Updates, die vom User vorgeschlagen wurden. Der genaue Inhalt variiert je nach Art und Menge der in der Waze App eingegebenen Information. *Wenn man auf einen ''Ort'' klickt, bei dem ein unbearbeitetes Update offen ist, erscheint im linken Bereich des WME die nachstehende Meldung. Wenn man darauf klickt, erscheint dieselbe Maske, wie wenn man auf das ''Ort'' Update Icon klicken würde. <br /> [[File:wme_places_update_pending_notice.png|center]]{{clear}} [[File:wme_place_update_new_details_long.png|thumb|right|Sehr langes ''Ort'' Update]] === Akzeptieren oder ablehnen? === Die Aufgabe der Waze Editoren ist es nun, die von den Usern vorgeschlagenen Updates zu akzeptieren oder abzulehnen. Der allgmeine Grundsatz für diese Entscheidung ist: ''" Ist der Großteil der vorgeschlagene Information im Update korrekt?"'' Wenn der User beim ''Ort'' Update alle Informationen ausfüllt, kann die Eingabemaske zur Kontrolle sehr lang sein (vgl. Thumbnail rechts). Auch wenn ein Teil der eingegebenen Daten falsch ist oder das vorgeschlagene Foto nicht verwendbar ist, kann der Editor nach dem ''akzeptieren'' des Updates das Foto oder falsche Daten immer noch korrigieren bzw. löschen. Es ist aber jedenfalls vorzuziehen, da schneller und auch dem User gegenüber ehrlicher, das grundsätzlich korrekte Update ''anzunehmen'' und nach dem Annehmen allfällige Probleme zu korrigieren, anstatt das ganze Update abzulehnen (und die korrekten Informationen dann selbst händisch einzufüllen). === Doppelte Orte === Wenn ein User ein Update für einen ''Ort'' vorschlägt, aber keinen bestehenden ''Ort'' dafür auswählt/auswählen kann, so wird im WME das Update als neuer ''Ort'' angezeigt. Wenn zwei User unabhängig voneinander einen neuen Ort melden, kann es im WME zur Anzeige zweier neuer ''Orte'' kommen. Derzeit gibt es keine Möglichkeit, im WME Informationen von verschiedenen Updates oder verschiedenen vorhandenen ''Orten'' (oder je einem von beiden) zusammenzulegen. Man muss daher händisch die Informationen von mehreren ''Orten'' und/oder Updates zusammenkopieren. ''Fotos kann man überhaupt nicht kopieren/verschieben.'' <U>Wenn man auf ein ''Ort''-Update stößt, das zu einer Verdopplung eines vorhandenen ''Orts'' führen würde</u>, wenn *das ''Ort''-Update mehr als nur ein Foto enthält und *das ''Ort''-Update verwendbare aktuellere Informationen enthält als der vorhandene ''Ort'' ist folgendes zu tun: #Akzeptiere das Update #Speichere #Kopiere die Aktuellere Information von dem gerade durch Speichern neu angelegten ''Ort'' zu dem ursprünglich schon bestehenden ''Ort'' #Lösche den im Schritt 1. gerade neu hinzugefügten Ort. Wenn die beiden oben angeführten Bedingungen nicht erfüllt sind, dann lehne das ''Ort'' Update gleich ab. <u>Wenn man auf zwei ''Ort''-Updates für denselben neuen ''Ort'' stößt</u> und in beiden Updates unterschiedliche verwendbare Informationen enthalten sind, so sollte man beide Updates akzeptieren, alle Informationen in einem ''Ort'' (dem mit Foto, wenn nur bei einem ein Foto dabei ist) zusammenkopieren und den anderen ''Ort'' löschen. {{clear}} === Private ''Orte'' === Wird ein ''Ort'' "Private Wohnstätte" (''Residential / Private'') gemeldet, so ist dieser '''nur mit Foto und vollständiger Adresse (Straße + Hausnummer)''' anzunehmen. Gegebenenfalls ist (auch hier) noch die genaue Position des Punktes zu überprüfen. Es sollte vermieden werden, im WME unnötige private ''Orte'' anzulegen, für diesen Zweck gibt es im WME die Möglichkeit Hausnummern einzutragen. '''Gemeldete Punkte KEINESFALLS auf public ändern und diese dann zu Flächen ändern! Gemeldete private Wohnstätten bleiben Punkte!''' == ''Orte'' Update FAQ == ===Wer kann ''Orte'' bearbeiten?=== User ab Level 2 können ''Orte'' in ihrer editierbaren Gebieten editieren. ===Was benötigt eine Moderation?=== *<u>Für neue ''Orte''</u>: Jeder neu angelegte ''Ort'', der von einem noch nicht vertrauenswürdigen Level 1 Editor angelegt wurde, braucht eine Bestätigung eines Level 2+ Users. *<u>Für Updates</u>: Jedes Update bei einem ''Ort'', der höher als das eigene Level gesperrt ist, benötigt ebenfalls die Bestätigung eines Editors mit höherem Level. *<u>Gemeldete Probleme</u>: Alle Probleme (zb problematische Fotos oder falsche Infos) können nur von einem User mit mindestens Level 2 editiert werden. ===Was ist ein vertrauenswürdiger User/Editor?=== Sobald einmal mehrere Fotos eines Users positiv bestätigt wurden, gilt er als vertrauenswürdig und kann von da an selber ''Orte'' editieren, sofern diese nicht für sein Level gesperrt sind. ===Welche Arten von ''Orten'' sollen akzeptiert werden?=== Eigentlich alles, was einen realen Ort repräsentiert. Wenn ein Waze User davon einen Nutzen haben kann, zahlt es sich schon aus. Ausnahmen sind Orte, welche private Nutzerinformationen enthalten, unangemessen oder sonst irrelevant sind. Wenn einige Infos des ''Ortes'' stimmen, dann ist der User, der diesen bestätigt und editiert, aufgefordert, andere fehlende Daten auch hinzuzufügen. ===Welche Fotos sollen akzeptiert werden?=== Alle Fotos, die den Ort zeigen, sind zugelassen. Fotos von Orten zu verschiedenen Tageszeiten sind noch besser, da zukünftig Uhrzeit abhängig die Fotos den Usern in der Waze App angezeigt werden sollen. Unangemessene Bilder, Bilder auf denen man Personen oder ganze Kennzeichen sieht oder Bilder vom Inneren eines Gebäudes sollten abgelehnt werden. Bedenkt bitte, dass durch das Ablehnen eines Fotos bzw eines neuen Ortes der User keine Punkte erhält. Durch ein mehrmaliges Ablehnen kann der User auch für das weitere Melden von ''Orten'' gesperrt werden. Im Zweifelsfall sollte daher das Foto akzeptiert und danach gelöscht werden. ===Kann ich ein Update teilweise ablehnen?=== Derzeit nicht. Wenn ein Teil des Updates korrekt ist, dann sollte das Update akzeptiert und im nachhinein die falschen Details korrigiert werden. ===Kann ich ein Foto zu einem anderen ''Ort'' verschieben?=== Nein. Diese Funktion gibt es weder im Editor noch in der APP. ===Kann ich Details von zwei ''Orten'' zu einem ''Ort'' zusammenfügen?=== Nein. Man kann nur händisch die Daten von einem zu einem anderen ''Ort'' kopieren. Wenn ein ''Ort'' ein Foto hat, ist es sinnvoll, diesen zu lassen und in diesen die Details zu kopieren. ===Kann ein User geblockt werden, wenn er neue ''Orte'' hinzufügt?=== Jeder User (vertrauenswürdig oder nicht) wird geblockt werden, wenn mehrere seiner neuen ''Orte'' oder Updates zu vorhandenen ''Orten'' abgelehnt werden. Man kann User auch manuell blockieren, wenn diese sich ihre gemeldeten ''Orte'' selber bearbeiten können und öfters nicht die Regeln befolgen. Das System beobachtet auch die Löschungen und kann User blocken, die systematisch mißbräuchlich ''Orte'' anlegen, die später von anderen gelöscht werden. ===Wer bekommt die Punkte, nachdem ein neuer ''Ort'' akzeptiert wurde?=== User, deren ''Orte'' zuerst bestätigt werden müssen, erhalten VORERST keine Punkte. Erst nachdem der ''Ort'' bestätigt wurde, werden die Punkte gutgeschrieben. Der User der den Ort akzeptiert oder ablehnt, bekommt normale Editierpunkte. ===Bekommt man für das Erstellen von Orten über die Waze App Punkte?=== Für das Editieren von Orten gibt es im WME sowie in der Waze App die gleiche Anzahl an Punkten. ===Werbeanbieter=== Einige Orte gehören Werbepartnern von Waze. Diese Orte sind dann für den Dauer der Werbepartnerschaft für alle User gesperrt. Man kann allerdings auch hier ein Update machen welches von der zuständigen Waze-Abteilung geprüft und bestätigt werden muss. ===Was ist die "Residental" Einstellung? Private und Öffentliche ''Orte''=== Das Hauptziel von Waze ist es, die Daten der Nutzer zu öffentlichen ''Orten'' zu erhalten und zu verbessern. Nachdem das Hinzufügen von ''Orten'' Spaß macht und auch etwas süchtig machen kann, gibt Waze den Usern auch die Möglichkeit, ihre privaten Orte einzutragen, damit diese nicht fälschlich als öffentliche eingetragen werden. Nach Privaten ''Orten'' kann nicht gesucht werden, auch wird die Identität des Users nicht angegeben, der sie angelegt oder Fotos hinzugefügt hat. Waze wird die hinzugefügten Fotos nur verwenden, um die Datenbank für Hausnummern und Orte zu verbessern und um sie den Leuten anzuzeigen, die explizit zu dieser Adresse fahren wollen. ===Die verschiedenen Attribute eines ''Orts'' === Die meisten Attribute sind selbsterklärend. Folgendes sollte jedoch beachtet werden: <u>Kategorien</u> Waze hat ca. 120 Kategorien ausgewählt basierend darauf, wonach die Waze User in der Vergangenheit gesucht haben. Das Ziel war, diese Kategorien möglichst weit zu fassen, es kann jedoch immer ''Orte'' geben, für die es keine exakt passende Kategorie gibt. Für diese ''Orte'' soll diejenige Oberkategorie verwendet werden, in der die passende Kategorie enthalten sein könnte. <u>Private / public</u> Öffentliche ''Orte'' können zu privaten gemacht werden. Benutze diese Funktion, wenn ein ''Ort'' fälschlich als Öffentlicher ''Ort'' eingetragen wurde. Private Orte enthalten nur die genaue Adresse und ein Foto, nicht jedoch die anderen Informationen, die es bei öffentlichen ''Orten'' gibt. '''Private ''Orte'' (damit sind Wohnhäuser gemeint) sollten NICHT zu öffentlichen geändert werden und schon gar nicht zu Flächen gemacht werden! Gemeldete Punkte BLEIBEN Punkte''' == Fläche-Punkt Kombination == Es gibt einige Situationen, wo es notwendig ist, Punkte und Flächen zu mischen. Ein Beispiel dafür ist ein Einkaufszentrum. Das Einkaufszentrum selbst wird als Orientierungspunkt eingezeichnet, die einzelnen Geschäfte hingegen als Navigationspunkte. Ein Einkaufszentrum, welches auf diese Weise eingezeichnet wurde, kann folgendermaßen aussehen. Rechts ein großes Einkaufszentrum (in diesem Fall die Shopping City Süd in Vösendorf) und links unten eine Einkaufszeile. Bei beidem kann man sich gut vorstellen, wie voll und überladen der Client wäre, wenn statt der Navigationspunkte für die einzelnen Geschäfte lauter Orientierungspunkte verwendet würden, die dann alle im Client angezeigt würden. {{clear}} [[File:SCS.jpg|center]] == Mehrfache Kategorien == *Einem ''Ort'' können mehrere Kategorien zugewiesen werden. *Die Hauptkategorie des ''Orts'' muss auch die erste sein, die eingetragen wird. *Die Hauptkategorie wird in einem dunkleren Blau dargestellt als die anderen Kategorien *Die Hauptkategorie entscheidet, ob der ''Ort'' als Punkt oder Fläche einzuzeichnen ist == Besondere Verwendungen von ''Orten'' == '''In Österreich:''' [[File:screenshot-place-ortsmitte.png|200px|thumb|right|Beispiel Ortsmitte]] Die Ortsmitte bzw. der Punkt möglichst nahe bei der Ortsmitte, den man mit dem Auto erreichen kann, kann mit einem dreieckigen Orientierungspunkt gekennzeichnet werden. So muss sich der User nicht darauf verlassen, wo Waze glaubt, dass die Ortsmitte liegt. Es wird vermutet, das von Waze generell die Mitte des City-Polygons als Ziel herangezogen wird, wenn nur ein Ortsname eingegeben wird. Dieser Punkt liegt oft aber auch in irgendeinem fernen Wohn- oder Industriegebiet, kilometerweit von der tatsächlichen Ortsmitte entfernt. Die Benennung hat einheitlich mit ''Irgendwasdorf Ortsmitte'' als Name (auch bei Städten, damit das im ganzen Land einheitlich ist und auch auf den Englischen Seiten des AT-wiki für Touristen angeführt werden kann) und ''Irgendwasdorf'' im AltName.<br> Als Kategorie ist nur die (Ober)Kategorie ''Andere'' zu verwenden, eine eigene Kategorie wurde beantragt. == Wann ist eine Fläche zu verwenden, wann ein Punkt? == Dies sind die für DACH (Deutschland, Österreich, Schweiz) gültigen Richtlinien, ob eine Fläche oder ein Punkt zu verwenden ist. {{Red|Die erste Kategorie eines Ortes bestimmt, ob er als Fläche oder als Punkt einzuzeichnen ist}} '''In der Spalte ''Art'' ist die international einheitliche Festlegung angeführt, wie ein ''Ort'' einzuzeichnen ist. In der Spalte Anmerkung sind österreichspezifische Erweiterungen dieser Definition angeführt'''. {{Red|Vorweg zu sagen ist: In der Kategorie '''Geschäfte und Dienstleistungen''' kann alles auch als Fläche eingezeichnet werden. Ausschlaggebend dafür ist, dass der ''Ort'' groß genug und für sich alleinestehend ist und keinem anderen Gebäude angehört. Also nicht jeden Greißler bzw Tante-Emma-Laden um die Ecke als Fläche einzeichnen}} <br /> == Die Kategorien == {| border="1" cellpadding="2" width="100%" style="font-size:small;" class="sortable" |- ! width="23%" style="background-color:#59899e; color:white" | Oberkategorie ! width="27%" style="background-color:#59899e; color:white" | Kategorie ! width="8%" style="background-color:#59899e; color:white" | Art ! width="42%" style="background-color:#59899e; color:white" class="unsortable" | Anmerkungen |- | Auto Dienstleistungen ''Car Services'' | Tankstelle ''Gas Station'' | Fläche | Viele Tankstellen haben auch einen Mini-Markt oder einen Bankomat. "Tankstelle" soll als erste Kategorie verwendet werden, dazu als weitere Kategorien alle anderen passenden (Bäckerei, Bankomat etc.). |- | Auto Dienstleistungen ''Car Services'' | Parkplatz ''[[Places/Parking lot|Parking Lot]]'' | Fläche | Es sollen nur wenige und nur bestimmte Parkplätze eingezeichnet werden, derzeit nur als Fläche (vgl den Abschnitt über [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Parkings_und_Parkpl.C3.A4tze|Parkplätze]]) |- | Auto Dienstleistungen ''Car Services'' | Garage / Automobil-Geschäft ''Garage / Automotive Shop'' | Punkt | |- | Auto Dienstleistungen ''Car Services'' | Auto-Waschanlage ''Car Wash'' | Punkt | [https://www.waze.com/de/editor/?env=row&lon=13.05472&lat=47.81954&layers=39&zoom=7&venues=8585694.85529262.2321355 Beispiel] |- | Auto Dienstleistungen ''Car Services'' | Ladestation ''Charging Station'' | Punkt | |- | | | | |- | Verkehr ''Transportation'' | Flughafen ''Airport'' | Fläche | [https://www.waze.com/de/editor/?env=row&lon=13.00127&lat=47.79185&layers=39&zoom=4&venues=8520158.85201579.301083 Beispiel] |- | Verkehr ''Transportation'' | Bushaltestelle ''Bus Station'' | Punkt | Benennung: "H Stationsname" Die Beschreibung sollte die abfahrenden Linien beinhalten. |- | Verkehr ''Transportation'' | Fähranleger ''Ferry Pier'' | Punkt | |- | Verkehr ''Transportation'' | Seehafen / Yachthafen / Hafen ''Seaport / Marina / Harbor'' | Fläche | Kann abhängig von der Größe auch als ''Punkt'' eingezeichnet werden. |- | Verkehr ''Transportation'' | U-Bahn-Station ''Subway Station'' | Punkt | Oberirdische größere Stationen können auch als Fläche gezeichnet werden. Bei unterirdischen nicht jeden Eingang extra einzeichnen sondern den der einer Straße am nähersten liegt. Bei der Suche kann man nicht unterscheiden welcher Eingang gemeint ist. |- | Verkehr ''Transportation'' | Bahnhof ''Train Station'' | Beides | Im englischsprachigen Raum wird kein Unterschied zwischen Bahnhof und Station gemacht. Aus diesem Grund werden bei uns große Bahnhöfe als Fläche und kleine Stationen sowie Straßenbahnstationen (wegen der fehlenden Kategorie) als Punkt gemappt. |- | Verkehr ''Transportation'' | Brücke ''Bridge'' | Fläche | |- | Verkehr ''Transportation'' | Tunnel ''Tunnel'' | Fläche | |- | Verkehr ''Transportation'' | Taxistandplatz ''Taxi Station'' | Punkt | |- | Verkehr ''Transportation'' | Kreuzung / Autobahnkreuz ''Junction / Interchange'' | Fläche | |- | | | | |- | Beruflich und öffentlich ''Professional and public'' | Hochschule / Universität ''College / University'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Schule ''School'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Kongress- / Veranstaltungszentrum ''Conventions / Event Center'' | Fläche | Kann abhängig von der Größe auch als ''Punkt'' eingezeichnet werden. |- | Beruflich und öffentlich ''Professional and public'' | Regierung ''Government'' | Punkt | |- | Beruflich und öffentlich ''Professional and public'' | Bibliothek ''Library'' | Punkt | |- | Beruflich und öffentlich ''Professional and public'' | Rathaus ''City Hall | Punkt | |- | Beruflich und öffentlich ''Professional and public'' | Organisation oder Vereinigung ''Organization or Association'' | Punkt | |- | Beruflich und öffentlich ''Professional and public'' | Gefängnis / Justizvollzugsanstalt ''Prison / Correctional Facility'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Gerichtsgebäude ''Courthouse'' | Punkt | |- | Beruflich und öffentlich ''Professional and public'' | Friedhof ''Cemetery'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Feuerwehr ''Fire Department'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Polizei ''Police Station'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Militär ''Military'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Krankenhaus / Medizinische Versorgung ''Hospital / Medical Care'' | Fläche | Für Krankenhäuser und medizinische Einrichtungen als Ganzes. Einzelne Stationen / Gebäude in einer solchen Einrichtung können als 'Punkt' eingezeichnet werden. |- | Beruflich und öffentlich ''Professional and public'' | Büros ''Offices'' | Beides | abhängig von der Größe |- | Beruflich und öffentlich ''Professional and public'' | Poststelle ''Post Office'' | Punkt | |- | Beruflich und öffentlich ''Professional and public'' | Religiöse Einrichtung ''Religious Center'' | Punkt | Kann abhängig von der Größe auch als ''Fläche'' eingezeichnet werden. |- | Beruflich und öffentlich ''Professional and public'' | Kindergarten ''Kindergarten'' | Punkt | |- | Beruflich und öffentlich ''Professional and public'' | Fabrik / Industrie ''Factory / Industrial'' | Beides | abhängig von der Größe |- | Beruflich und öffentlich ''Professional and public'' | Botschaft / Konsulat ''Embassy / Consulate'' | Fläche | |- | Beruflich und öffentlich ''Professional and public'' | Informationsstelle ''Information Point'' | Punkt | |- | | | | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Kunst und Handwerk ''Arts & Crafts'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Bank / Finanzen ''Bank / Financial'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Sportausrüstung ''Sporting Goods'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Buchhandlung ''Bookstore'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Fotografie ''Photography'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Autohaus ''Car Dealership'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Mode und Bekleidung ''Fashion and Clothing'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Gemischtwarenladen / Quartierladen ''Convenience Store'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Körperpflege ''Personal Care'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Kaufhaus ''Department Store'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Apotheke / Drogerie ''Pharmacy'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Elektronik ''Electronics'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Blumen ''Flowers'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Möbel / Haushalt ''Furniture / Home Store'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Geschenke ''Gifts'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Fitness Studio / Fitness ''Gym / Fitness'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Schwimmbad ''Swimming Pool'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Haushalt- und Eisenwarenhandlung ''Hardware Store'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Markt ''Market'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Supermarkt / Lebensmittel ''Supermarket / Grocery'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Juwelier ''Jewelry'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Reinigung / Chemische Reinigung ''Laundry / Dry Cleaning'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Einkaufszentrum ''Shopping Center'' | Fläche | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Musikladen ''Music Store'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Tierhandlung / Veterinärwesen ''Pet Store / Veterinarian'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Spielwarenladen ''Toy Store'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Reisebüro ''Travel Agency'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Geldautomat ''ATM'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Geldwechsel ''Currency Exchange'' | Punkt | |- | Geschäfte und Dienstleistungen ''Shopping and services'' | Autovermietung ''Car Rental'' | Punkt | |- | | | | |- | Speisen und Getränke ''Food and drink'' | Restaurant / Gastwirtschaft / Gasthaus ''Restaurant'' | Punkt | |- | Speisen und Getränke ''Food and drink'' | Bäckerei ''Bakery'' | Punkt | |- | Speisen und Getränke ''Food and drink'' | Dessert ''Dessert'' | Punkt | |- | Speisen und Getränke ''Food and drink'' | Café ''Coffee shop'' | Punkt | |- | Speisen und Getränke ''Food and drink'' | Fast Food / Schnellimbiss / Würstelstand ''Fast Food'' | Punkt | |- | Speisen und Getränke ''Food and drink'' | Lebensmittelbereich ''Food Court'' | Punkt | |- | Speisen und Getränke ''Food and drink'' | Bar ''Bar'' | Punkt | |- | Speisen und Getränke ''Food and drink'' | Eis ''Ice Cream'' | Punkt | |- | | | | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Kunstgalerie ''Art Gallery'' | Punkt | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Kasino ''Casino'' | Fläche | Kann abhängig von der Größe (zB ein kleines Kasino in einem Haus in der Stadt) auch als ''Punkt'' eingezeichnet werden. |- | Kultur und Unterhaltung ''Culture & entertainment'' | Club ''Club'' | Punkt | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Sehenswürdigkeit / Historische Stätte ''Tourist Attraction / Historic Site'' | Punkt | Bei markanten größeren Gebäuden oder ganzen Flächen, die eine Sehenswürdigkeit / historische Stätte darstellen, kann auch ''Fläche'' verwendet werden. |- | Kultur und Unterhaltung ''Culture & entertainment'' | Kino ''Movie Theater'' | Punkt | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Museum ''Museum'' | Punkt | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Musikveranstaltungsort ''Music Venue'' | Punkt | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Künstlerischer Veranstaltungsort ''Performing Arts Venue'' | Punkt | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Spielhalle ''Game Club'' | Punkt | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Stadion / Arena ''Stadium / Arena'' | Fläche | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Themenpark ''Theme Park'' | Fläche | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Zoo / Aquarium ''Zoo / Aquarium'' | Fläche | Kann abhängig von der Größe auch als ''Punkt'' eingezeichnet werden. |- | Kultur und Unterhaltung ''Culture & entertainment'' | Rennbahn ''Racing Track'' | Fläche | |- | Kultur und Unterhaltung ''Culture & entertainment'' | Theater ''Theater'' | Punkt | |- | | | | |- | Andere ''Other'' | Baustelle ''Construction Site'' | Fläche | Ist zur Kennzeichnung von Straßenbaustellen nicht mehr in Verwendung, seit es TBR (time based restrictions) bzw. Sperren (''closures'') gibt. |- | | | | |- | Unterkunft ''Lodging'' | Hotel ''Hotel'' | Punkt | |- | Unterkunft ''Lodging'' | Herberge ''Hostel'' | Punkt | |- | Unterkunft ''Lodging'' | Campingplatz / Wohnwagensiedlung ''Camping / Trailer Park'' | Fläche | Kann abhängig von der Größe auch als ''Punkt'' eingezeichnet werden. |- | Unterkunft ''Lodging'' | Ferienhaus / Hütte ''Cottage / Cabin'' | Punkt | |- | Unterkunft ''Lodging'' | Gästezimmer ''Bed & Breakfast'' | Punkt | |- | | | | |- | Im Freien ''Outdoors'' | Park ''Park'' | Fläche | |- | Im Freien ''Outdoors'' | Spielplatz ''Playground'' | Punkt | Abhängig von der Größe auch als Fläche |- | Im Freien ''Outdoors'' | Strand ''Beach'' | Fläche | |- | Im Freien ''Outdoors'' | Sportplatz ''Sports Court'' | Punkt | Abhängig von der Größe auch als Fläche |- | Im Freien ''Outdoors'' | Golfplatz ''Golf Course'' | Fläche | |- | Im Freien ''Outdoors'' | Platz ''Plaza'' | Punkt | |- | Im Freien ''Outdoors'' | Promenade ''Promenade'' | Punkt | Fraglich, ob dieser Typ überhaupt eingezeichnet werden soll. |- | Im Freien ''Outdoors'' | Malerische Aussicht / Aussichtspunkt ''Scenic Lookout / ViewPoint'' | Punkt | |- | Im Freien ''Outdoors'' | Teich / Weiher ''Pool'' | Punkt | |- | Im Freien ''Outdoors'' | Skigebiet ''Ski Area'' | Fläche | Nur die Talstation der Lifte sind einzuzeichnen, nicht das gesamte Skigebiet über alle Berge und Täler einzufärben. |- | | | | |- | Natürliche Merkmale ''Natural features'' | Insel ''Island'' | Fläche | |- | Natürliche Merkmale ''Natural features'' | Meer / See / Reservoir ''Sea / Lake / Pool'' | Fläche | |- | Natürliche Merkmale ''Natural features'' | Fluss / Bach ''River / Stream'' | Fläche | |- | Natürliche Merkmale ''Natural features'' | Wald / Hain ''Forest / Grove'' | Fläche | Nur für größere zusammengehörende Waldflächen, die idealerweise auch noch einen eigenen Namen haben (zB Wienerwald, Böhmerwald, Kobernaußerwald) und als eingezeichneter Ort für die Orientierung von Nutzen sind, nicht für jede kleine Ansammlung von Bäumen am Straßenrand. Die Fläche sollte sich an den tatsächlichen Rändern und der tatsächlichen Ausdehnung des Waldes orientieren (bitte keine undefinierbaren riesigen grünen Flecken, die alles mögliche zudecken). |- | Natürliche Merkmale ''Natural features'' | Bauernhof ''Farm'' | WEDER NOCH | |- | | | | |- | Private Wohnstätte ''Residential / Private'' | | Punkt | |} [xx Beispiel] 5cce5450b8c76b6560b9a9ae2337e87686bc679e 0 94 12021 2017-10-29T21:25:19Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Einleitung= In unbearbeiteten Gebieten, wo die Karte vom Basis-Karten-Import (Base-Map) stammt, sin…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Einleitung= In unbearbeiteten Gebieten, wo die Karte vom Basis-Karten-Import (Base-Map) stammt, sind alle Straßen auf der gleichen Höhe, in der Regel Ebene 0. Sie sind teilweise durch Kreuzungen auf der gleichen Ebene verbunden, wo eigentlich Über- oder Unterführungen (Brücken, Tunnels etc.) sein sollten. Dies kann zu falschen und sogar gefährlichen Navigationsanweisungen führen, wie z.B. von einer Brücke direkt auf die Autobahn abbiegen oder dergleichen. Damit der Routing-Server versteht, dass eine Überführung nicht eine Autobahn kreuzt oder eine Brücke nicht mit einer normalen Straße darunter verbunden ist, muss der Editor, der die Karte bearbeitet in der Lage sein, solche Straßen in der Höhe unterscheiden zu können. Als Hilfsmittel dienen hier: *Der Höhenwert einer Straße ([[Erstellen_und_bearbeiten_eines_Segments#Ebene|Segment-Ebene]] im Karteneditor) *Die [[WME_Schnellstart-Anleitung#Br.C3.BCcken|Brücken-Funktion]]. =Grundsatz= Generell sollte das Langstreckennetz (Autobahnen, Bundesstraßen, Landesstraßen) und auch die Hauptstraßen nicht durch unnötige Kreuzungen unterbrochen werden. Die über- oder unterführenden Straßen sind aufzuteilen und mit Segment-Ebenen zu versehen. Unnötige Kreuzungen von Brücken der Basis-Karte sind zu entfernen. =Wie Über- und Unterführungen definiert werden= Im Karteneditor gibt es einen Eigenschaft dafür, welche jedes Segment besitzt: Die Segment-Ebene. Standardmäßig besitzt jedes Segment Ebene 0, ob es nun vom Basis-Karten-Import stammt, aufgezeichnet oder neu eingezeichnet wurde im Editor. Wenn zwei Straßen, überlappen, die sich nicht kreuzen sollten, müssen beide Segmente in der Höhe unterschieden werden. So werden auch Fehlermeldungen im Karteneditor verhindert. =Bedingungen= * Die Brücken-Funktion funktioniert nur für zwei Segmente auf einmal. Man kann nicht 3 oder mehr Segmente mit dieser Funktion bearbeiten. * Solange die Straßen keine Richtung besitzen, also "Unbekannt" erscheint kein Brückensymbol, da die Kreuzung nicht entfernt werden kann. * Folgende Eigenschaften müssen bei beiden Segmenten übereinstimmen: Land, Staat (wo definiert), Stadt, Straßenname. Der Straßentyp, die gültige Richtung oder ob die Segmente gesperrt sind, spielt dabei keine Rolle. =Eine Überführung erstellen= In diesem Bild kreuzt eine Autobahn eine darüber liegende Hauptstraße auf beiden Seiten. [[Image:Brücke_1.png|540px]] Als erstes muss Du [[WME Schnellstart-Anleitung#Mehrfach-Auswahl|zwei Segmente auswählen]], die Du mit der Brücken-Funktion verbinden willst. Wenn alle Eigenschaften übereinstimmen erscheint ein Brücken-Symbol im Karteneditor auf der Kreuzung, wo sich die Segmente berühren. [[Image:Brücke_2.png|540px]] Mit dem Anklicken des Brücken-Symbols passieren drei Dinge: # Die beiden ausgewählten Segmente verbinden sich zu einem. # Der Level des verbundenen Segments steigert sich um eine Stufe höher als das höchste der beiden zuvor ausgewählten Segmente. # Die anderen Segmente die jetzt darunter liegen (hier im Beispiel die Autobahn) verbinden sich ebenso zu einem Segment. Es ist nun ein Segment entstanden, das Du durch zwei Segmente verbunden hast. Um die Brücke oder Überführung fertigzustellen, musst Du nun auf der unteren Seite noch einmal das selbe machen. Meistens reicht ein einmaliges Verbinden durch die Brücken-Funktion, für manche Kreuzungen kann es auch mehr als zwei Verbindungen geben. Wiederhole nun die oben beschriebene Vorgehensweise. [[Image:Brücke_3.png|540px]] Wenn alles funktioniert hat, sieht das Ganze so aus wie im nächsten Bild. An der Stelle, wo die Kreuzungen waren, sind nun zwei Geometrie-Punkte. Dies ist normal und Du kannst diese auch [[WME_Tipps_und_Tricks#Geometrie-Punkte_schnell_entfernen|entfernen]], wenn dies notwendig ist oder sie dazu gebrauchen, die Straße auszurichten. Dies ist natürlich abhängig davon, ob dies nötig ist und das Segment an die GPS-Punkte oder Luftaufnahmen darunter angepasst werden muss. [[Image:Brücke_4.png|540px]] Das letzte Bild zeigt an, dass die zwei Autobahn-Segmente keine Kreuzungen mehr besitzen, wo sie vorher mit der darüber liegenden Straße verbunden waren. Korrigiere nun die Segment-Ebenen, das Hauptstraßen-Segment muss in diesem Fall Ebene 1 besitzen und die Autobahn-Segmente Ebene 0. ''Da Du zweimal die Brücken-Funktion hintereinander verwendet hast, besitzt das Hauptstraßen-Segment Ebene 2 und eines der Autobahn-Segmente Ebene 1'' Wenn Du die Segment-Ebenen korrigiert hast, musst Du nur noch speichern. [[Image:Brücke_5.png|540px]] =Tunnel= Tunnel werden mit der Ebene "-1" versehen, damit Waze sie auch als Tunnel erkennt und automatische Kartenfehler durch das System ausgeschlossen werden. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] a3b9f97533e261203194c8608b91dfa4494c11d4 0 95 12023 2017-10-29T21:26:43Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Einleitung= Straßen können aus verschiedenen Gründen temporär, oder komplett gesperrt sein, i…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Einleitung= Straßen können aus verschiedenen Gründen temporär, oder komplett gesperrt sein, in einer oder beiden Richtungen: * Baustellen * Naturkatastrophen * Örtliche Veranstaltungen Unter Umständen kann eine Straße für Stunden, Tage, Wochen oder Jahre gesperrt werden. Aufgrund der Länge einer Sperrung entscheiden wir, wie die Karte angepasst wird. =Stunden, Tage, Wochen= Wenn die Sperre nur für ein paar Stunden oder auch ein paar Wochen besteht, dann benütze die Funktion [[Meldungen_erstellen#Closure|Melden > Sperrung]] in der Waze-App. Du musst Dich dazu vor Ort befinden, um eine Sperrung über die App zu melden. Der beste Weg um eine Sperre einzutragen ist das dafür vorgesehene Formular zu nutzen [http://goo.gl/s4nyXc DACH - Straßensperren]. =Monate, Jahre= Wenn eine Straße für längere Zeit gesperrt ist, aufgrund einer Langzeitbaustelle oder anderer Gründe, ist es das Beste eine zeitliche Beschränkung einzurichten. Diese können auch für nur eine Richtung eingerichtet werden (z.b. bei temporären Einbahnstraßen) =Täglich für bestimmte Stunden= Ist eine Straße täglich oder an mehreren Tagen für eine gewisse Zeit gesperrt, ist es das Beste mit zeitlich beschränkten Abbiegeverboten zu arbeiten, Informationen dazu findest Du weiter unten. =Anmerkung zur Dauer aller Sperrungen= Im Moment werden die Karten ''täglich'' aktualisiert, auf allen Infrastrukturen. Abhängig davon, wann Du die Sperrung bearbeitet hast, ist die Änderung schon innerhalb 2 Tage auf der Karte der Waze-App enthalten. Eingerichtete Sperren (sogenannte Closures) sind sofort aktiv, ohne Update. * Wenn nur eine Spur gesperrt ist, muss die Karte '''nicht''' angepasst werden. * Wenn eine Straße langsamer befahren wird als sonst, wird Waze die Geschwindigkeiten nach unten korrigieren und ggf. automatische Meldungen anzeigen. * Wenn es eine Umfahrung gibt, wird Waze lernen, wenn Du da entlang fährst. * Du musst alle anschließenden Straßen kontrollieren, ob sie auch korrekt bearbeitet sind (Richtungen und Abbiegungen), damit Waze eine optimale Route finden kann. =Zeitlich beschränkte Fahrverbote= Zeitlich beschränkte Abbiege- oder Fahrverbote ermöglichen Waze das Routing von Fahrzeugen durch Abbiegungen oder Straßen zu steuern. Dies kann basierend auf Zeit, spezifischen Tagen oder (in Zukunft) Fahrzeugtypen beschränkt werden. Klassische Beispiele sind Spuren für öffentlichen Verkehr, Abbiegeverbote während Hauptverkehrszeiten, Richtungsänderungen, saisonale Sperrungen, bewegliche Brücken oder Fährverbindungen. * Fährverbindungen können als Mautstraßen definiert sein und gleichzeitig mit beschränkten Fahrverboten markiert sein, abhängig von den Betriebszeiten. Schau dazu in die länderspezifischen Wikis. * Feldwege, die nicht für den öffentlichen Verkehr frei sind, brauchen keine zeitlich beschränkten Fahrverbote. Diese sind als Privatstraße zu definieren. * Privatstraßen sind Privatstraßen, auch diese sind nicht mit zeitlich beschränkten Fahverboten zu versehen. * Informationen zu Privatstraßen findest Du [[Fußwege_und_Privatstraßen | hier]] == Übersicht == Es gibt 3 verschiedene Methoden um den Verkehrsfluß zu steuern: # [[Mega events]] # Temporäre Straßensperrungen in der App oder im Editor # Zeitlich beschränkte Abbiegeverbote Zeitlich beschränkte Fahrverbote basieren auf: # Einem Segment, das den Verkehrsfluß in eine oder beide Richtungen steuert # Spezifischen Abbiegungen von einem auf ein anderes Segment Beide können weiter beschränkt werden basierend auf Kombinationen von: # Tageszeit, Wochentag oder spezifischen Datumsbereich Beispiele: * Keine PKWs erlaubt zwischen 09.00h - 15.00h * Abbiegen verboten zwischen 07.00h - 09.00h und 16.00h - 18.00h an Werktagen * Fahrbahnen die tageszeitabhängig ihre Fahrtrichtung ändern Es ist sehr wichtig, dass die Beschränkungen sehr sorgfälltig definiert werden, damit keine fehlerhaften Routings entstehen. Kontrolliere sie lieber zweimal, so ersparst Du den Wazern auf der Straße unnötigen Ärger. == Segmente == [[Image:Segment info restrictions button highlight.jpg|right]] Wenn kein Verkehr durch ein Segment (Straße) läuft oder bestimmte Fahrzeugtypen nicht erlaubt sind, kannst Du die Beschränkung direkt für das betreffende Segment definieren. Dies ist einfacher, als jede Abbiegung, die von anderen Segmenten auf das Segment führt einzeln zu verbieten. Manche Beschränkungen betreffen nur eine Fahrtrichtung, oder die Fahrtrichtung ändert in die Gegenrichtung zu einer bestimmten Tageszeit. Beschränkungen können über die Schaltfläche "Beschränkung hinzufügen/bearbeiten" bearbeitet werden, oder via Tastaturkürzel '''T'''. Dies öffnet das Bearbeitungsfenster für die Beschränkungen. Segmente, die in beiden Richtungen befahrbar sind zeigen zwei Reiter an: "A nach B" und "B nach A", welche sich auf die Richtung der Segmente beziehen. Buchstaben A und B für das ausgewählte Segment. Der Text unterhalb bezieht sich auf das ausgewählte Segment [[Image:Segment restriction list add button highlight_sm.gif|right]] Klicke auf die Schaltfläche "Beschränkung hinzufügen" um eine neue Beschränkung hinzuzufügen. Schau unter [[#Beschr.C3.A4nkung_hinzuf.C3.BCgen|Beschränkung hinzufügen]], um mehr Informationen zu erhalten. Du kannst mehrere Beschränkungen pro Segment hinzufügen, für verschiedene Tageszeiten oder Wochentage. [[Image:Restrictions copy to other side.jpg|right]] Wenn Du die Beschränkung erfasst hast, kannst Du sie auch ganz leicht für die Gegenrichtung kopieren. Benutze dazu die Schaltfläche "Kopiere gleiche Beschränkung für die Gegenrichtung". Ansonsten wird die Beschränkung nur für eine Richtung gültig sein. Wenn eine Beschränkung erstellt wurde, kannst Du sie bearbeiten [[File: Pencil_icon.jpg]] oder entfernen [[File: X_icon.jpg]] mit der entsprechenden Schaltfläche. {{clear}} === Mehrfachauswahl von Segmenten === Du kannst auch mehrere Segmente gleichzeitig mit einer Sperrung belegen. Halte die Ctrl-Taste (Cmd auf Mac) und wähle die Segmente aus, oder verwende das Tastaturkürzel '''m'''. [[Image:Restrictions multiple segments.gif]] Ein paar Sachen, die Du beachten musst bei einer Mehrfachauswahl: * Achte auf Einbahnstraßen. * Segmente können Unterschiedliche Erstellrichtungen besitzen A->B oder B->A * When multiple segments are selected with different restrictions set on them, they will appear in a different section of the panel under the title: 'These restrictions only apply to some of the segments selected:' Click the ‘Apply to all’ link to the right of the restriction line to propagate the restriction to all the selected segments. == Abbiegungen == Wenn nur einzelne Abbiegungen nicht erlaubt sind, halte Dich an die folgenden Anweisungen. === Alle Abbiegungen zu jeder Zeit verbieten === Abbiegungen, die für alle Fahrzeuge zu jeder Zeit verboten sind, erhalten einen roten Pfeil. Sie brauchen keine zeitlich beschränkten Abbiegverbote. [[Image:Lotsa turns.jpg]] Klick einfach auf den grünen Pfeil und er ändert auf rot. * Informationen zu den Abbiegungen findest Du [[WME_Schnellstart-Anleitung#Abbiegungen | hier]]. === Zeitlich beschränkte Abbiegeverbote === Wenn einzelne Abbiegungen nicht zu jeder Zeit oder für alle Fahrzeuge verboten sind, kannst Du diese Abbiegungen von Segment zu Segment beschränken. Das gleiche gilt für Abbiegungen, die für alle Fahrzeuge nur zu bestimmten Zeiten verboten sind. Um eine Beschränkung hinzuzufügen, fahre mit der Maus auf den gewünschten Pfeil. Klick auf das Uhr-Logo und das Bearbeitungsfenster öffnet sich. [[Image:Restriction arrow green.gif]] Die Uhr erscheint nur auf grünen Pfeilen. [[Image:Turn-restriction-list-add-button-highlight.gif]] Klick auf den Button "Beschränkung hinzufügen". Schau unter [[#|Beschränkung hinzufügen]], wie man diese genau definiert. Du kannst einer Abbiegung mehere Beschränkungen für verschiedene Tageszeiten oder auch Wochentage zuweisen. Wenn Du die Beschränkungen definiert hast und "Übernehmen" angeklickt hast, siehst Du einen gelben Pfeil. Das bedeutet, dass die Beschränkung nun aktiviert ist. Speichern nicht vergessen. [[Image:Restriction arrow yellow mouseover.gif]] Um das Bearbeitungsfenster für eine bestehende Beschränkung zu öffnen, musst Du einfach wieder auf die Uhr klicken. Wenn Du nur den gelben Pfeil anklickst, wird er rot. Wenn Du den roten Pfeil nun nochmals anklickst, wird er wieder gelb und die vorher gespeicherten Beschränkungen erscheinen wieder. == Beschränkung hinzufügen == Für Segment- und Abbiegebeschränkungen verwenden wir jeweils das selbe Bearbeitungsfenster. Einmal wird es über die Segment-Eigenschaften geöffnet, das andere Mal über den Abbiegepfeil. [[Image:Restrictions empty panel.gif]] Configure the restriction as required using the guidelines described for each setting. After configuring the restriction as required, press the '''Add''' button on that panel to save the restriction and return to the Time based restrictions panel. Continue adding restrictions in the same way to cover combinations that may only restrict a few house per day, but at different times of day. === Days of week === Select the days of the week that the restriction will be active. Use the '''Select all''' or '''Select none''' link to to more quickly change all the check boxes. The default is all days of the week. Your display order for the days will depend upon your country settings in your browser and may not exactly match the image above. === Time of day === For restrictions that apply all day long, use the default setting of '''All day'''. If the restriction is for only certain periods of time during the day, then select the '''From''' radio button to allow the time to be changed. You can click the hours or minutes fields to enter times directly, or click the clock icon next to the time to enable input panels. The time is entered in [http://en.wikipedia.org/wiki/24-hour_clock 24-hour format], meaning AM and PM are not used. To convert from 12 hour time to 24 hour time, use the following table: {| class="wikitable" style="margin: 1em auto 1em auto;" |- ! align="left" | 12 hour time !! 24 hour time !! How? |- | align="left" | 12:00 AM (midnight) - 12:59 AM | align="left" | 0:00 - 0:59 | align="left" | subtract 12 from hour |- | align="left" | 1:00 AM - 11:59 AM | align="left" | 1:00 - 11:59 | rowspan="2" align="left" | do nothing |- | align="left" | 12:00 PM (noon) - 12:59 PM | align="left" | 12:00 - 12:59 |- | align="left" | 1:00 PM - 11:59 PM | align="left" | 13:00 - 23:59 | align="left" | add 12 to hour |} Minutes, of course, remain the same. For example, a schedule of 10:00 AM to 3:00 PM would instead be entered as 10:00 to 15:00; a schedule of midnight to noon (12:00 AM to 12:00 PM) would instead be entered as 0:00 to 12:00. The time that should be entered is the local time of the road as would be displayed on the local signs. The Waze server already knows the local time zones and will schedule the restriction correctly. Daylight savings time is automatically accounted for as long as the Waze client app is properly set to the correct local time. ==== Entering midnight ==== If a scheduled restriction is between 8:00 PM and Midnight, then enter "20:00 - 23:59". Technically you can also enter "20:00 - 00:00" to get the same result. ==== Crossing midnight ==== If a restriction occurs only during night time hours and opens in the morning e.g., restricted between 10 PM and 5 AM, then enter the From time as 22:00 and the To time as 05:00. You will notice an information box that says the restriction will end of the following day. If this restriction is only on a certain day of the week, e.g., Saturday night and Sunday night, then select the day of the week for Sat and Sun matching the start of the restriction. There is no need to include Monday because it will be automatically covered. Including the Monday check box would then add a third day starting at 10 PM Monday. === Date range === [[Image:Restrictions dates selector.gif]] The default setting is '''Every week''' meaning there is no limit to the date range so as soon as you add the restriction it will be active every week until it is removed. Optionally you can select the radio button for '''Range''' of dates to limit the restriction to a certain number of days. Press the button displaying the date to display two calendars. The one one the left shows the start date and the calendar on the right shows the end date of the restriction. Note these date are inclusive meaning the restriction will include both dates (and all the ones in between) when determining the restriction. When you have selected the date range press the green '''Apply''' button. The date range is displayed in '''DD/MM/YYYY''' format. To remove the date range, simply select the '''Every week''' radio button again. Again the end date will consider the entire day based on any time settings also configured. If the time crosses midnight, the next day will automatically be included for that time period and then the restriction will no longer be active after that ending time. === Vehicle type === There are some situations that only restrict certain vehicle types from passing through the turn or segment. Examples of this include no truck zones. {{Red|((Insert some photos of real-world signs))}} Also, some turns may be taken by no traffic ''except'' certain vehicles. Examples of this include HOV lanes, bus stops, and truck-only exit ramps. For example, for an HOV-2 restricted road, you might check all vehicle types except public transportation, HOV-2, HOV-3, and motorcycles. {{Red|((Insert some more photos))}} The default condition is '''All vehicle types''' are included in the restriction, but if only certain vehicles are going to be restricted, press the '''(Edit)''' link next to '''Restriction for all vehicle types''' to bring up the vehicle type selector. [[Image:Restrictions vehicle types.jpg]] Add a check mark only the vehicles that are not permitted during the restriction period and leave the other types unchecked. Use the '''Select all''' or '''Select none''' link to change all the check boxes. ''REMEMBER: These are <u>restrictions</u>. The selected vehicle types will be restricted. The unselected vehicle types will be admitted.'' {{Red|NOTE:}} The Waze client app does not differentiate between different vehicle types, so these settings do not have any affect on routing. === Text Description === Leave a description for the nature of the restriction. If the restriction is the result of signs or markings, make note of this. If the restriction is the result of construction or road work, leave details about the closure. {{Red|NOTE:}} There is a 100-character limit in the Description field. Entering more than that will result in a "General Error" upon trying to save. == Examples == The following examples cover specific situations to provide more guidance. Some of the examples below will be turn based restrictions, but the method is the same for the segment restrictions. === Date range results === The following table includes example date range combinations and the resulting restrictions that it would generate: {| |- |'''Days of the week''' |'''Time Range''' |'''Date Range''' |'''Restriction Result''' |- |Sunday |All day |12.1.2014 - 12.31.2014 |Every Sunday on December 2014, from 00:00 until 23:59:59. |- |Monday - Friday |09:00-11:00 |Every Week |Every weekday from 9am to 11am. |- |Thursday |23:00-03:00 |Every Week |Every Thursday from 23:00 until every Friday at 03:00 |- |All |All day |7.3.2015 - 7.15.2015 |From July 3rd 2015 at 00:00 until July 15th at 23:59:59 |} === Simple time based restrictions === For a turn or segment that is restricted (not allowed) between 10 am and 2 pm daily, click the radio button next to "From", then enter "10:00" and "14:00" as the start and end times of the restriction. [[Image:Restrictions 10-14.jpg]] Click "Add" to add the restriction. You will be returned to the Time based restrictions panel. The panel should now reflect the added restrictions. [[Image:Restrictions list 10-14.jpg]] For a turn that is restricted between 7 and 9 am, and again between 4 and 6 pm, add the restrictions one-by-one as instructed above. When added, the panel should look like this. {{Red|((Insert image of panel with 7-9 and 16-18 restrictions added - n peters to bienville example))}} ==== Overnight time based turn restrictions ==== Time-of-day restriction periods may cross midnight. For a turn that is restricted between 8 pm and 6 am, enter the From time as 20:00 and the To time as 6:00. {{Red|((Insert image of panel with 20-23:59 and 0-6 restrictions added - bourbon street example))}} === Date-based turn restrictions === Some restrictions may also only be in place on certain days of the week. For a turn that is restricted "weekends", check only the boxes for "Sat" and "Sun". [[Image:Restriction SatSun only.jpg]] === Time-and-date-based turn restrictions === For a turn that is restricted "2 pm to 4 pm, weekdays", when adding the restriction, uncheck the boxes next to "Sat" and "Sun", and enter "14:00" and "16:00" in the time boxes. [[Image:Restriction m-f 14-16.jpg]] === Time-of-year and holiday turn restrictions === Some restrictions may only be in place during certain times of year. If on a specific date and time, set the appropriate combination. At this time, there is no way to schedule a yearly repeating holiday restriction. You must enter each year manually. === Reversible road === Reversible roads are roads whose travel direction depends on the time of day, to allow more lanes of travel into or out of a city in order to handle the additional vehicle load during rush hours. On the Waze map, a reversible road is set up as a 2-way road, and then the allowed travel directions are set up as restrictions. This is a bit tricky because Waze uses the idea of ''restrictions,'' which is the opposite of ''allowed.'' For example, say a road allows travel northbound only between the hours of 6AM to 11AM. Those are the allowed hours of travel that direction. In the Waze restrictions setup, we would have to ensure that travel in that direction is ''restricted from 11:01AM to 5:59AM.'' ==== Reversible roads with vehicle type restrictions ==== Some reversible roads may also be restricted to certain vehicle types. A common example of this is the reversible HOV lane. Some cities have reversible roads set up that are also HOV lanes. Two examples are in Seattle and are the I-90 and I-5 Express Lanes. These lanes reverse travel direction depending on the time of day, but these lanes are also HOV lanes, so you aren't allowed on them unless your vehicle meets the requirements. Below are the current setup for the I-5 Express Lanes in Seattle, WA, based on [http://www.wsdot.wa.gov/Northwest/King/ExpressLanes/Weekdays.htm|the published schedules] by the Washington Department of Transportation. [[Image:I-5 express seattle a-b restrictions list.jpg]] [[Image:I-5 express seattle b-a restrictions list.jpg]] While the WSDOT webpage is very simple what the schedule is, only having two entries, to translate that into restrictions is much more complicated. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 88854c3e0ae8cb65ac537bea683d63583dd16dd5 0 96 12024 2017-10-29T21:27:06Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] "Verstreute Orte" entstehen, wenn ein Ortsname mehrmals auf der Karte erscheint oder an einer Stell…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] "Verstreute Orte" entstehen, wenn ein Ortsname mehrmals auf der Karte erscheint oder an einer Stelle, wo er nicht hingehört. Es kann sich auch um falsche Namen handeln oder fehlerhafte Einträge wie "H" anstatt "Hamburg". Dies geschieht, wenn der Editor die Namen nicht korrekt aus der Dropdownliste zuweist. Waze versucht, alle Straßen mit dem gleichen Landes-, Bundesland-, Stadt- und Straßennamen miteinander zu verbinden. Dadurch entstehen die farbigen [[WME_Tipps_und_Tricks#St.C3.A4dte-Poliygone|Orts- oder Städte-Polygone]], die ca. 95% aller Straßen umfassen, die einem Ort auf der Karte zugewiesen sind. Der Karteneditor kann dank Abfrage der Entfernung beim Editieren, den Radius einschränken. Man kann einen Ortsnamen bis maximal 25 Kilometer, von dem Ort entfernt, wo er bereits existiert anlegen. Regional ist das aber noch möglich. Und solche Einträge tauchen auch noch immer auf. Im folgenden zeigen wir am Beispiel der Stadt Fayetteville, die in der Gegend von Charlotte, NC als verstreuter Ort erscheint, wie man das korrigiert. == Identifiziere das Problem == [[Image:CitySmudge01.jpg|200px|right]] Merke oder notiere Dir den fehlerhaften Namen der Stadt, den Du entdeckt hast oder mach einen Screenshot davon. Typischerweise findet man sie beim Fahren mit der Waze-App an Orten, wo sie nicht hingehören. Du kannst sie auch leicht im Karteneditor finden, indem Du alle Ebenen, außer Straßen und Städte ausschaltest. == Suche im Editor nach Fehlern in der Nähe == [[Image:DupeCity1.jpg|300px|right]] Starte den Karteneditor in der Gegend, wo Du das Problem gesehen hast. Zoome ein paarmal hinein und heraus und schau Dir die Ortsnamen an, die auf der Karte erscheinen. In der Straßen-Ebene werden nicht alle Ortsnamen bei jeder Zoomstufe angezeigt. Wenn Du den falschen Namen gefunden hast oder zwei gleiche Namen, dann mach weiter beim [[#Aufst.C3.B6bern_des_betreffenden_Segments|Abschnitt 5]].<br> ''Anmerkung: Oft sind doppelte Namen zwei verschiedenen Ländern zugewiesen.'' == Suche in der weiteren Umgebung nach Fehlern == Gib den gesuchten Ortsnamen ohne weitere Angaben in das Suchfeld ein und starte eine Suche, worauf eine Liste mit Suchergebnissen erscheinen sollte. Wähle von den angezeigten Einträgen einen nach dem anderen aus und suche dort durch Zoomen und zusätzliches Verändern des Kartenausschnitts, ähnlich wie im Absatz 2 beschrieben. Vergiss nicht, das für alle der passenden Suchergebnisse zu wiederholen. Wenn Du die gesuchte Stadt gefunden hast, mach weiter beim [[#Aufst.C3.B6bern_des_betreffenden_Segments|Abschnitt 5]].<br> ''Anmerkung: So kann man auch gut Schreibfehler in Ortsnamen entdecken.'' == Suche den Ort in der Waze-App == Ändere dafür als erstes das Farbschema "Karteneditor" * Menü-> Optionen-> Anzeigeeinstellungen-> Farbschema Zoome auf der Karte hinein und heraus und verschiebe die Ansicht bis an den Rand einer Stadt. Halte Ausschau nach Linien, die den verstreuten Ort darstellen und vom Polygon der Stadt wegführen. Verstreute Orte werden nicht bei jeder Zoomstufe angezeigt, also vergrößere und verkleinere den Ausschnitt und drehe die Ansicht 360° um die Stadt herum. Hier ein Beispiel, welches westlich von Charlotte, NC gefunden wurde. Beachte den Namen des verstreuten Orts (Fayetteville) auf einer sehr dünnen schattierten Linie von Ost nach West: :[[Image:Smudge_Client.jpg]] Versuche ohne die Zoomstufe zu ändern, entlang dieser Linie, das Ende zu finden, das nicht zu der Stadt gehört. Dort wo die Linie aufhört ist der Endpunkt des verstreuten Orts. Wenn der Name des verstreuten Orts im Polygon einer Ortschaft verschwindet mach weiter beim [[#Aufst.C3.B6bern_des_betreffenden_Segments|Abschnitt 5]]. Wenn die Linie verschwindet oder Du das Ende nicht gefunden hast musst Du evtl. mehr herauszoomen. Wenn Du immer noch nichts gefunden hast kann es sein, dass es ein neueres Problem ist, das noch nicht auf der Karte aktualisiert wurde oder ein älteres Problem, das bereits gelöst wurde und von der Karte noch nicht verschwunden ist. == Aufstöbern des betreffenden Segments == Wenn Du den Ort lokalisieren konntest, musst Du beim Namen hinein zoomen und dort Deine Suche fortsetzen. Das problematische Segment ist meist unter oder in der Nähe des Namens. [[Image:CitySmudge01zoom.jpg|200px|right]] Es kann sein, dass es sich nur um ein Segment handelt oder auch um mehrere. Sie können in der Nähe sein oder auch einen Kilometer auseinander liegen. Schau Dich um, auch wenn Du denkst, dass Du bereits alle Segmente kontrolliert hast. Mit aktivierter Städte-Ebene ist es leicht die falschen Segmente zu finden, sie folgen in der Regel den farbigen Polygonen. Die Ränder der Polygone grenzen die falschen Segmente ein.<br> ''Anmerkung: Es gibt auch [[Community_Plugins,_Extensions_and_Tools#WME_Color_Highlights_for_Landmarks_and_Segments|Skripte]], die Dir helfen verstreute Orte oder falsche Segmente zu finden. == Untersuche beide Enden des verstreuten Orts! == Es kann sein, dass ein verstreuter Ort von einem korrekten Ort wegführt. Beispiel: Fayetteville, NC erscheint in Fayetteville, AR. Oder Du findest einen verstreuten Ort, der an beiden Enden falsch ist Beispiel: Fayetteville, AL erscheint in Fayetteville, NC und Fayetteville, AR. Wenn Du einen Ort ohne Bundesland oder der Eintrag lautet "Anderes", dann ist der Ort fast sicher an beiden Enden falsch. Auch wenn hier von einem verstreuten Ort an beiden Enden geredet wird, kann er auch mehrere Enden haben. Es gab einen verstreuten Ort in Columbus der ein gigantisches Dreieck über drei Staaten in Amerika gebildet hatte, anstatt nur einer dünnen Linie.<br> ''Anmerkung: Im [[Glossar#DACH|DACH-Raum]] ist das Feld für Bundesländer im Karteneditor noch nicht aktiv.'' ::[[Image:Columbus_before_2.jpg]] ::[[Image:Columbus_before_1.jpg]] == Korrekturen vornehmen == Wenn Du die nötigen Rechte hast, korrigiere die Segmente. Wenn Du keine Rechte hast versuche einen [[Der_Area_Manager|Area-Manager]] zu kontaktieren. Falls dies nicht zum gewünschten Ziel führt, melde Dich im Forum des betreffenden Landes. Poste dort für die betroffenen Regionen [[Glossar#Permalink|Permalinks]] == Fehlendes Bundesland == Sobald dieses Feld aktiv ist, wird dieser Abschnitt vervollständigt. == Korrekturen überprüfen == Damit Du deine Änderungen auf der Karte überprüfen kannst, musst Du die Aktualisierung abwarten. Die Dauer, bis der verstreute Ort verschwunden ist kann variieren. Es kann sein, dass das Problem mit nur einer Aktualisierung der Karte gelöst ist oder es verkleinert sich nur. Wenn dies der Fall ist, hat es evtl. noch mehrere falsche Segmente auf der Karte und Du musst das ganze nochmals wiederholen, bis alle Fehler bereinigt sind. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 6a9805a3c3f29f9263fe6b5c41539913f22f8dcc 0 8 12026 12025 2017-10-29T21:33:33Z Popel22 24 /* Seiten auf Englisch */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Hilf mit Waze zu verbessern]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] dca605776b7966dcb8d20e949a9ce0801ebf8c71 12031 12026 2017-10-29T21:37:02Z Popel22 24 wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] (veraltet) * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Hilf mit Waze zu verbessern]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] c9cd3581117de1905910fb998058c07d5650953b 12032 12031 2017-10-29T21:38:23Z Popel22 24 /* Problemlösung */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] (veraltet) * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Glossar]] * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] f5e576494df103761342662ad61e24d5c1edec1f 12034 12032 2017-10-29T21:41:05Z Popel22 24 /* Problemlösung */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] (veraltet) * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Glossar]] (oder lieber [[usa:Glossary|glossary]] ? ) * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Anleitung für Benutzer|Anleitung Waze App Version 3+]](muss übersetzt werden) * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] c0215f35b4836b33e9146bbb6de17bac755b4b2b 12037 12034 2017-10-29T21:43:19Z Popel22 24 /* Sonstige Links */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] (veraltet) * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Glossar]] (oder lieber [[usa:Glossary|glossary]] ? ) * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Zeichne Straße auf]] * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] ada4a1b3f52a6d57fa22d4c62bfef09467ec1dc2 12038 12037 2017-10-29T21:43:53Z Popel22 24 /* Sonstige Links */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] (veraltet) * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Glossar]] (oder lieber [[usa:Glossary|glossary]] ? ) * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Zeichne Straße auf]] (veraltet) * [[Die soziale Vernetzung]] * [[Die Waze Pendler Gruppen‎]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] b9e4a023948b6f896e8071d43aabc84013e94233 12042 12038 2017-10-29T21:47:03Z Popel22 24 /* Sonstige Links */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [[Österreich|Wiki für Österreich]] * [[Deutschland|Wiki für Deutschland]] * [[Switzerland|Wiki für die Schweiz]] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] (veraltet) * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Glossar]] (oder lieber [[usa:Glossary|glossary]] ? ) * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Zeichne Straße auf]] (veraltet) * [[Die soziale Vernetzung]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] 0fb0c5ae73c1af12001d6dd9f309b3c2fdeb4b4d 12045 12042 2017-10-29T21:51:12Z Popel22 24 /* Anleitung zum Bearbeiten der Karte */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder: * [https://wazeopedia.waze.com/wiki/Austria Wiki für Österreich] * [https://wazeopedia.waze.com/wiki/Germany Wiki für Deutschland] * [https://wazeopedia.waze.com/wiki/Switzerland Wiki für die Schweiz] ==Waze Map-Editor Anleitung== * [[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] * [[WME Schnellstart-Anleitung]] * [[WME Update Requests]] * [[WME Map Problems]] * [[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== * [[Die beste Vorgehensweise beim Bearbeiten der Karte]] * [[Rechte zum Bearbeiten der Karte]] * [[Sperren von Straßen (Locking)]] * [[Soft und Hard Turns]] * [[Kreuzungen]] * [[Abbiegespuren]] * [[Abbiegeanweisungen über Pfeile]] * [[Erstellen und bearbeiten eines Segments]] * [[Erstellen und bearbeiten eines Kreisverkehrs]] * [[Orte und Navigationspunkte]] * [[Unterführungen und Brücken]] * [[Fußwege und Privatstraßen]] * [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] * [[Verstreute Orte]] * [[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== * [[Häufig gestellte Fragen]] * [[Ablauf der Aktualisierungsprozesse]] * [[Wie Waze Routen kalkuliert]] * [[Mein Dashboard]] * [[Die Server Bänke]] * [[Der Debug Mode]] (veraltet) * [[Wann stelle ich ein Frage im Forum]] * [[Hilf mit die Karte zu vervollständigen]] * [[Mail an den Support]] * [[Diskussionsforum]] * [[Glossar]] (oder lieber [[usa:Glossary|glossary]] ? ) * [[Privatsphäre]] (im Aufbau) * [[Suchcodes]] ==Sonstige Links== * [[Zeichne Straße auf]] (veraltet) * [[Die soziale Vernetzung]] * [[Der Waze Chat]] * [[RSS Feeds]] * [[Feed List]] [[Category:Anleitung]] 13e9ec7ebe4de230cd79ce6bfb1983ab93048a83 0 97 12027 2017-10-29T21:34:17Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Thematik "Benennen von Straßen" wurde in der Vergangenheit oft sehr kontrovers diskutiert. Um…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Thematik "Benennen von Straßen" wurde in der Vergangenheit oft sehr kontrovers diskutiert. Um die Sache besser zu verstehen, muss man sich zunächst ansehen, wie Waze Routen berechnet. Hier eine kurze Zusammenfassung, die einen ersten Einblick in die Routing-Logik von Waze bieten soll. Dazu gilt zu sagen, dass Waze selbst keinesfalls den Routing Algorithmus veröffentlichen wird. Warum? Niemand gibt seine besten Karten aus der Hand! =Anfragen an den Routing-Server= Wenn Du eine Route berechnen lässt, wird die Anfrage an den Routing-Server gesandt. Die berechnete Route wird dann an Deinen Client zurückgesandt. Die berechnete Route ist von Deinen Einstellungen im App-Menü "Navigation" abhängig (schnellste/kürzeste Route, Autobahnen oder Mautstraßen meiden usw.) =Routenberechnung im Client= Der Client führt simple Routenberechnungen selbständig durch. Diese Berechnungen beinhalten keine Echtzeit-Verkehrsdaten. Sie werden nur aufgrund der Durchschnitte der Segmente seit dem letzten Update geführt, welche auch bereits im Client-Cache hinterlegt sein müssen. Eine Berechnung im Client findet nur statt, wenn keine Netzwerkverbindung besteht während einer Routenberechnung. =Straßentypen und Kreuzungen= Das Routing ist auch abhängig von Straßentypen, die aufgrund der Distanzen ins Routing miteinbezogen werden (eine Tabelle dazu findest Du weiter unten). Ebenso wird die Anzahl der Kreuzungen in Betracht gezogen, um von Punkt A nach Punkt B zu gelangen. In der Regel gilt für eine Kreuzung ein Penalty (Zeitzuschlag) von 5 Sekunden bei der Berechnung einer Route (Fake-Nodes ausgenommen = Kreuzungen, die nur 2 Segmente verbinden und keine andere Abbiege-Möglichkeit bieten). Das Routing zieht längere Segmente mit weniger Kreuzungen (auch Fake-Nodes) kürzeren Segmenten mit mehreren Kreuzungen vor. =Zeit und Geschwindigkeit= Wenn ein Wazer die Segmente befährt, werden die Geschwindigkeiten vom System registriert und ein Durchschnitt gespeichert. Bei der Berechnung der Routen, werden die Geschwindigkeiten der einzelnen Segmente berücksichtigt. Ebenso wird die Zeit berücksichtigt, die benötigt wird, um ein Segment zu durchfahren. Wurde ein Segment nie befahren, ist auch keine Durchfahrts-Geschwindigkeit in diesem Segment gespeichert. ==Standard-Geschwindigkeiten== Für den Routing-Server gelten Standard-Geschwindigkeiten für unbefahrene Straßen. {| class="wikitable" style="background:none; font-size:100%; align: left" border="0" |- | - '''Freeway''' || 130 km/h |- | - '''Major Highway''' || 110 km/h |- | - '''Minor Highway''' || 90 km/h |- | - '''Primary Street''' || 50 km/h |- | - '''Street''' || 50 km/h |} ==Aktuelle Fahrgeschwindigkeiten== Waze registriert Echtzeit-Verkehrsmeldungen wie Staus und beginnt eine neue Strecke zu berechnen, da die aktuellen Geschwindigkeiten mit der gespeicherten Geschwindigkeit in den Segmenten verglichen werden. Mit dieser Methode wird man um Staus herum geroutet. Hierzu gilt zu sagen: Wenn Du eine Route planst, die mehr als 30 Minuten dauert, werden nicht die aktuellen Verkehrsdaten am Endpunkt in die Berechnung einfließen. Ein Beispiel: Wenn Du eine Route von München nach Hamburg planst, werden nicht die aktuellen Staus in Hamburg in die Berechnung einfließen. Eine neue Berechnung am aktuellen Ort löst dieses Problem. =Fernstreckennetz= Das sogenannte "Least-Cost-Routing" durch das Straßennetz von Waze ist eine sehr rechenintensive Angelegenheit. Damit es dennoch klappt, innerhalb einer möglichst kurzen Zeit eine Route zu generieren, benutzt Waze eine Vielzahl von Tricks. Einer dieser Tricks ist die Verwendung des Fernstreckennetzes, also jene Straßen, die in die Kategorie Highway fallen: Alle Freeways, Ramps, Major- und Minor Highways sind in einem Netz zusammengefasst, das nur für längere Routen verwendet wird. Bei Planung einer Route versucht Waze mit Hilfe aller befahrbaren Straßen, dieses Fernstreckennetz zu erreichen, dafür wird in einem Umkreis von bis zu 25 km gesucht. Einmal auf diesem Fernstreckennetz angelangt, findet Waze schnell eine Route, bevor es auf den letzten 25 km dann wieder über alle befahrbaren Straßen plant. Dieser Vorgang wird für jeden möglichen Übergang in und aus dem Fernstreckennetz wiederholt, bis am Ende eine optimale Route übrigbleibt. Ein weiterer Trick ist die Gruppierung von mehreren Segmenten, entsprechend ihres Straßennamens und City-Eintrags. Je mehr Segmente hierbei berücksichtigt werden müssen, desto länger dauert auch die Kalkulation. Ist eine bestimmte Anzahl an Segmenten erreicht, bricht der Routing-Server die Berechnung ab. Deswegen werden z.B. Autobahnen mittlerweile zu möglichst großen Segmenten zusammengefasst (einheitlicher Name, kein City-Eintrag). Da es wohl auch niemanden gibt, der z.B. am Autobahnkilometer 157 wohnt, wäre ein Eintrag im City-Feld auch sinnlos. =Penalty-System= Für die Erstellung einer Route verwendet Waze auch ein System von Penalties (Zeitzuschläge). Das Penalty-System ist dafür verantwortlich, den schnellsten Weg zu finden. Es eliminiert mögliche Routen, indem es für die Berechnung mehr Zeit (pro Segment oder Kreuzung) vergibt als erwartet. '''Penalty-Typen:''' * Nicht befahrbare Wege wie: Walking-Trail, Pedestrian Boardwalk, Railroad, Runway erhöhen die voraussichtliche Ankunftszeit (ETA) um 1 Stunde. * "Parking-Lot-Road" und "Private Road" erhalten ebenfalls einen höheren Penalty, da sie nicht für durchgehendes Routing zur Verfügung stehen. * Toll-Roads: Wenn "Avoid toll roads" in der Waze-App eingeschaltet ist, wird der Penalty für die Segmente um ein vielfaches multipliziert; ohne diese Einstellung im Client ist die Mautstraße für Waze eine normal befahrbare Straße! * U-Turns: Scharfwinklige Kurven sowie U-Turns selbst erhalten einen enormen Zeitzuschlag für die Ankunftszeit. Einen Penalty erhalten auch U-Turns, die aus drei Segmenten bestehen. Wenn das U-Turn-Segment länger als 15 Meter lang ist, wird kein Penalty hinzugefügt. '''Fahrtrichtung:''' * Fahrtrichtung des Segments nicht gesetzt (Unknown) +0,30 Sekunden zusätzlich. Dies gilt für Amerika und alle Länder mit Base-Map. * Richtung automatisch gesetzt bei Fahrten entgegen der Fahrtrichtung: Für jede Fahrt entgegen der Fahrtrichtung wird ein 30-Sekunden-Zuschlag zur ETA addiert. '''Strecken-Berechnung für lange Distanzen:'''<br> Welche Straßentypen Waze ins Routing einbezieht, ist von den Distanzen abhängig. * 0–15 km – Alle Straßentypen werden ins Routing einbezogen.<br>''Anmerkung'': Das bezieht sich auch auf die Kategorie "Non-Drivable" * 15–20 km – Alle Straßentypen außer Streets. * 20–30 km – Alle Straßentypen außer Streets und Primary Streets. * 30–200 km – Nur Minor, Major und Freeways. * mehr als 200 km – nur Freeways.<br> Mehr Infos dazu in der [https://world.waze.com/support/ Quick Help] auf der Support-Seite. Gib in der nanoRep Box das Wort "Penalty" ein. =Bearbeiten von Kreuzungen legt diese eindeutig fest= In Gegenden mit [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] gibt es einen Unterschied zwischen Kreuzungen, die vom User bearbeitet oder geupdatet wurden und den Base-Map-Kreuzungen, die nie bearbeitet oder befahren und mit dem Base-Map-Upload-Prozess erstellt wurden. Diese Kreuzungen erscheinen, als wären die Abbiegungen verboten, sie können jedoch geroutet werden, als ob sie erlaubt wären. In der Regel bevorzugt der Routing-Algorithmus Segmente und Kreuzungen, die vom User gesetzt wurden. Aber falls der Weg viel länger wird oder keiner vorhanden ist, wird trotzdem auch über nicht eindeutig gesetzte Abbiegungen geroutet. Eine Straße in beiden Richtungen befahrbar zu machen ändert den Status der Kreuzungen nicht. Wird eine Kreuzung bearbeitet, ist sie gültig, wie in Gegenden ohne Base-Map. Die Kreuzung wird nicht gelockt, wenn nur eine Abbiegung geändert wird. <br> Diskussion darüber [http://www.waze.com/forum/viewtopic.php?f=186&t=10319] FIXME: Die Diskussion ist nicht für jeden User lesbar. =Parking-Lot-Road= Die "Parking-Lot-Road" wird verwendet, um - wie der Name schon sagt - Parkplätze zu erstellen. Auch werden sie vom Routing-Server sozusagen ausgeschlossen. Waze hat im Juni 2012 den Algorithmus so angepasst, dass durch einen Penalty verhindert wird, durch die Parkplätze zu navigieren. Der Penalty besteht beim Übergang vom Parkplatz auf das normale Straßensystem. Das heißt: Es kann auf den Parkplatz und aus ihm heraus navigiert werden aber nicht durch den Parkplatz hindurch, um ggf. eine Abkürzung zu erzeugen. Es ist daher nicht sinnvoll, auf Parkplätzen die Straßentypen zu mischen. Ein Parkplatz hat durchgängig "Parking-Lot-Road" als Straßentyp. =Verkehrsmeldungen= Für die Erstellung von Verkehrsmeldungen bedient sich Waze anderer Methoden, indem die City-Namen aus der Umgebung herangezogen werden. Das korrekte Bearbeiten der Autobahn-Anschlussstellen ist daher zwingend nötig. Weiterführende Straßen ''sollten'' nach Möglichkeit City- und Straßennamen enthalten, um eine Meldung so genau wie möglich einzugrenzen. ==Staumeldungen== Staumeldungen (farbcodiert) veranlassen das Routing eine neue Strecke zu berechnen, um den Stau zu umfahren. Farbcodierte Segmente (ausgeleuchtet) entstehen wenn die gespeicherte Durchschnitts-Geschwindigkeit eines Segments unterschritten wird. Auch erscheint beim Unterschreiten der Geschwindigkeit ein Popup mit der Frage, ob man sich im Stau befindet. '''Melden von Staus wirkt sich auf das Entstehen eines farbcodierten Segments aus:'''<br> Meldet ein User einen Stau auf einer Straße, beschleunigt dies das Entstehen eines farbcodierten Segments, sofern dabei auch die gespeicherte Geschwindigkeit unterschritten wird. Die Staumeldung eines Benutzers über das Client-Menü alleine genügt nicht, um farbcodierte Segmente zu erzwingen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 4e58480808af0b0fcc4c15e1d9eead4853517dff 0 98 12028 2017-10-29T21:34:37Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Link zum Dashboard== https://www.waze.com/de/dashboard =Dashboard= ==Dashboard (perönliche Pr…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Link zum Dashboard== https://www.waze.com/de/dashboard =Dashboard= ==Dashboard (perönliche Profilseite)== Hier werden alle Funktionen Deines Dashboards (Deine Profilseite) erklärt. Im Dashboard sind all Deine persönlichen Informationen und die Statistik Deiner Fahrten und Punkte zu sehen. Du kannst nur darauf zugreifen, wenn Du Dich auf der Waze-Website angemeldet hast. Falls Du Dich angemeldet hast und die Statistik leer ist, kontrolliere, ob Du auf dem richtigen [[Die Server Bänke | Server]] angemeldet bist. Ausserdem ist das Dashboard in den ersten 1-2 Wochen eventuell noch nicht aktuell da die Server Deine Fahrten, Rechte usw. erst initialisieren und anlegen müssen. [[Image:Mein_Dashboard.png|700px]] <br> Wenn Du Dich angemeldet hast, siehst Du die verschiedene Sektionen. * Persönliche Details * Meine Fahrtenstatistik * sowie oben links Deinen Usernamen, Punkte und Rang ==Persönliche Details== * Hier werden deine persönlichen Angaben angezeigt. Du hast die Möglichkeit Deine Mailadresse, das Passwort, den Benutzernamen, Geburtsdatum, Stadt, Geschlecht usw. zu ändern. Änderungen werden nach Anklicken des "Speichern"-Buttons aktiv. [[Image:personal_details.png]] ===Facebook=== '''Facebook-Funktionen sind im Dashboard nicht mehr konfigurierbar. Bitte stell die entsprechende Verknüpfung zu Deinem Facebookprofil über die Waze-App her.''' ==Meine Fahrtenstatistik== Hier kannst Du Deine [[Häufig_gestellte_Fragen#Wie_werden_die_Punkte_berechnet.3F|Punkte]] und Deinen Rang einsehen resp. Deine eigene persönliche Statistik verfolgen. Waze wird die Statistik einmal am Tag aktualisieren, und Dein Rang kann sich so täglich ändern. Es kann sein, dass Deine Punkte nicht täglich aktualisiert werden. Dann lies den [[Ablauf der Aktualisierungsprozesse]] und verschaffe Dir Klarheit. [[Image:ranks_points.png]] * '''Karten-Bearbeitungen''' wird nur gezählt, wenn Du die Karte bearbeitest. * '''Alle Berichte''' sind alle Meldungen, die Du während der Fahrt ans System gesendet hast. * '''Aufgezeichnete Kilometer''' sind Strecken, die Du über die App [[Zeichne Straße auf|aufgezeichnet]] hast. * '''Gefahrene Kilometer''' zeigt die Summe aller von Dir mit Waze gefahrenen Kilometer. * '''Behobene Aktualisierungsanfragen''' sind die [[WME_Oberfläche_und_Steuerelemente#Update_Requests_.28Aktualisierungs-Anfrage.29|Update-Requests]], die Du auf der Karte gelöst hast. * '''Beiträge im Forum''', sind alle Posts, die Du im [http://world.waze.com/forum Forum] geschrieben hast. Kommunikation wird bei uns groß geschrieben! Für 3 Posts im Forum gibt es 2 Punkte. * '''Geknabberte Straßen in Meter''' Zählt das Befahren neuer Straßen (Pacman-Roads) <br> '''Dein Rang''' ist Dein Rang - basierend auf allen Wazern weltweit. Dein landesbezogener Rang ist nur in der App sichtbar. * Bist Du in Deutschland zu Hause, wirst Du in den Top 50 der deutschen Landesstatistik aufgeführt und auf der Top 50 der Serverstatistik für den World-Server - sofern Du die nötige Punktezahl besitzt, um in die Top 50 zu gelangen! Nach 2-3 Wochen (z.B. im Urlaub) wird man in der Landesstatistik des betreffenden Landes (z.B. im Urlaub) eingestuft - sichtbar in der App. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] d9101977e85eeb0b27179a5717a929960a1b11b2 0 99 12029 2017-10-29T21:35:03Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] '''Waze läuft auf drei verschiedenen Servern:''' <br> Nur für die USA und Kanada (Alias: WWW-…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] '''Waze läuft auf drei verschiedenen Servern:''' <br> Nur für die USA und Kanada (Alias: WWW-Server, NA-Server) http://www.waze.com <br> Nur für Israel ( Alias: IL-Server) http://www.waze.co.il <br> Der Rest der Welt (Alias: World-Server, INTL-Server, ROTW - Rest of the World) http://world.waze.com <br> Diese funktionieren unabhängig voneinander. Bei [[Wann stelle ich ein Frage im Forum|Fragen und Problemen]] ist es daher nötig zu Wissen auf welchem Server man arbeitet. Wenn man http://www.waze.com besucht leitet der Server normalerweise die Anfrage an den richtigen Server weiter. Falls das [[Mein Dashboard|Dashboard]] keine Punkte anzeigt oder man auf dem [[Der Waze Map-Editor|Karteneditor]] keine Karte sieht: '''URL kontrollieren!''' ==Direktes Login im Forum auf dem World Server== * http://world.waze.com/forum/ucp.php ==Direktes Login im Dashboard auf dem World Server== *http://world.waze.com/dashboard/ ==Direktes Login für Gruppen und Punkteliste auf dem World Server== *Gruppen: http://world.waze.com/dashboard/groups/ *Scoreboard: http://world.waze.com/dashboard/scoreboard/ <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 6ba90c00ccf5ab98cc81d9385b14886967f1d5ff 0 100 12030 2017-10-29T21:36:22Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Der debug mode== Der "debug mode" wird verwendet, um mehr Daten aus der Waze App zu sammeln und a…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Der debug mode== Der "debug mode" wird verwendet, um mehr Daten aus der Waze App zu sammeln und an die Waze Server zu übermitteln. Dies ist vor allem bei Problemen und Bugs in der Waze Anwendung auf deinem Smartphone von Vorteil. Bitte schaue zuerst im Forum nach, ob dein Problem nicht schon einmal behandelt wurde. Es kann auch sein, dass Du bei spezifischen Problemen vom Support im Forum gebeten wirst deine Probleme im "debug mode" zu protokollieren und an Waze zu übermittlen. Das passiert normalerweise nur bei unbekannten oder nicht nachvollziehbaren Problemen, die im Forum diskutiert werden. ==Debug mode einschalten== Um in den debug mode zu gelangen wähle im Menü "Navigiere". <br> [[Image:Debug1.png]] <br> Gib in die Suchleiste 2##2 ein und tippe auf "Suchen". <br> [[Image:Debug2.png]] <br> Es erscheint folgende Meldung: <br> [[Image:Debug3.png]] <br> Im Menü steht nun oben links debug. <br> [[Image:Debug4.png]] ==Logfiles senden== Nach dem Hochladen der Protokolle, sende eine Nachricht an den Support via [http://www.waze.com/support/ Quick Help] auf der Support-Seite mit Datum und Zeit wann die Protokolle gesendet wurden, und der Beschreibung deines Problems. Der Support wird dein Problem so schnell wie möglich bearbeiten. Beachte, dass im "debug mode" eine Menge Daten gesammelt werden, es ist also von Vorteil, wenn Du die Protokolle über das WLAN-Netz versendest. Um die Protokolle zu senden wähle im Menü "Optionen". <br> [[Image:Log1.png]] <br> Danach wähle "Hilfe". <br> [[Image:Log2.png]] <br> Als nächstes wähle "Protokoll schicken" <br> [[Image:Log3.png]] <br> Fahre fort indem Du auf "Ja" tippst <br> [[Image:Log4.png]] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] d465b39e1c5420f09f48f231613cb1450f74c071 0 101 12033 2017-10-29T21:38:44Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =AMS/ASM= :Dies bezeichnet die Area-Manager-Selbstverwaltung, in englischen Beiträgen auch SM (Sel…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =AMS/ASM= :Dies bezeichnet die Area-Manager-Selbstverwaltung, in englischen Beiträgen auch SM (Selfmanagement) genannt =ASR= :''Automatic Speech Recognition'' - Die Fähigkeit Sprachbefehle in Aktionen auf dem Smartphone oder Tablet umzuwandeln. =Client= :Dies ist die Waze-App auf Deinem Smartphone oder Tablet. =Cookies, cookie munching= :Cookies sind die Punkte auf unbestätigten Straßen (Pacman Roads). Cookie Munching (Road Munching, Straßen munchen, Straßen knabbern) bedeutet, dass man diese Straßen befährt und die kleinen Punkte frisst. Ebenso werden die Straßen bestätigt und gelten für den Server als fahrbar. =Country-Manager= :Country-Manager oder CMs sind Editoren, die erweiterte Rechte besitzen. Sie können Landesweit uneingeschränkt an der Karte arbeiten. Sie können alle Locks der Levels 2-5 entsperren. =DACH= :'''''D'''eutschland, '''A'''ustria, '''C'''onfederatio '''H'''elvetica'' - Dies bezeichnet die deutschsprachige Gemeinschaft von Deutschland, Österreich und der Schweiz). Jedes Land der DACH-Gemeinschaft besitzt eigene Wiki-Seiten und Forenteile. =Devs= :''Developers'' - Die Devs sind die Entwickler oder Programmierer der Waze-App oder des Waze Map-Editors =Editieren= :Die Karte bearbeiten mit dem Waze Map-Editor. =Editor= :Derjenige, der die Karte bearbeitet. Als Editor kann aber auch der Waze Map-Editor (Karteneditor) gemeint sein, daher auf den Kontext achten. =End-Node= :Eine End-Node ist eine Kreuzung am Ende einer Sackgasse. Sie wird vom System benötigt, damit aus der Straße navigiert werden kann. =Directionality/Direktionalität= :Bezeichnet die Richtung einer Straße. =Freeway oder Freeways= :Autobahnen oder einzelne Autobahn-Segmente, je nach Kontext (in diversen Ländern auch Schnellstraßen). Schau in die länderspezifischen Wikis! =Geometrie= :Das Aussehen oder die Form einer Straße. Jede Straße besteht aus geraden Liniensegmenten. Diese können beliebig kurz oder lang sein und ermöglichen auch Kurven :Die Geometrie beschreibt auch die Form der Landmarks. =Geometrie-Node/Geometrie-Punkte= :Segment [[Image:Segment geometry node.png]] [[Image:Segment intergeometry node.png]] Orientierungspunkt [[Image:Landmark node.png]] [[Image:Segment intergeometry node.png]] :Die Geometrie-Nodes sind da, um das Aussehen oder eben die Geometrie der Segmente und Orientierungspunkte zu verändern oder anzupassen. Sie können beliebig durch ziehen mit der Maus verschoben werden. Mit '''"D"''' kann eine Geometrie-Node gelöscht werden, wenn die Maus diese berührt. :Inter-Geometrie-Nodes sind die kleinen weißen Punkte. Zieht man an den kleinen weißen Punkten werden sie zu großen. =Ghost Segmente, Ghost Segments, Geister Segment= :Als Ghost Segment bezeichnen wir Straßen, die durch Sync Errors (Synchronisationsfehler) nicht mehr auswählbar sind oder nach einer Veränderung nicht gespeichert werden können. Vielfach entstehen sie, wenn man eine Straße anbindet und durch eine Kreuzung verbindet. Solche Segmente müssen dem Support gemeldet werden, gehe dazu auf die [http://world.waze.com/support Support-Seite] und erstelle in der nanoRep-Box (Quick Help) eine Nachricht mit Permalink der Gegend, in der sich dieses Segment befindet. =Junction= :[[Image:Junction_normal.png]] :Dies bezeichnet eine Kreuzung, dort wo die Straßen miteinander verbunden sind; manchmal wird auch fälschlicherweise von einer Node geredet. *[[Image:Junction selected.png]] Ausgewählte und editierbare Kreuzung<br> *[[Image:Uneditable_junction.png]] Ausgewählte und nicht editierbare Kreuzung (Keine Rechte).<br> *[[Image:junction_unsaved.png]] Kreuzung geändert, aber noch nicht gespeichert =KISS= :Bedeutet "Keep it simple and stupid" und mahnt uns zur Vereinfachung der Waze-Karte. Unnötig komplizierte Straßenverläufe und Kreuzungen produzieren wirre Ansagen und erschweren ein vernünftiges Routing, dies gilt es zu verhindern. Zudem hilft es uns auch mögliche Fehlerquellen zu minimieren. Schau Dir die Seiten [[Die beste Vorgehensweise beim Bearbeiten der Karte]] und [[Base Map 1.0]] an. =Map tile, tile, tiles update= :Die Waze-Karte ist in einen Raster von 1km² grossen Quadraten aufgeteilt, welche Tiles oder Map-Tiles genannt werden. Die Änderungen werden auf einer pro-tile Basis gemacht. Änderungen, die an einer Tile oder Teilen davon gemacht wurden, werden auf dem Server als geänderte Tile registriert und diese wird beim Update neu gebildet. =Mappen= :Als mappen bezeichnet man auch das Bearbeiten oder Editieren der Karte mit dem Karteneditor =MP= :''Map Problem'' - Kartenfehler der durch das System erkannt wurde. Diese sind im Karten-Editor sichtbar und können so weiterverarbeitet werden. =Ortspolygone= :[[WME_Tipps_und_Tricks#St.C3.A4dte-Poliygone|Die Städte-, Orts- oder auch City-Polygone]] enthalten oder umfassen ca. 90-95% aller Straßen, denen der gleiche Stadtname zugeordnet ist. Sie werden im WME farbig dargestellt, um die Grenzen der Orte anzuzeigen. In der App sind sie grau im Farbschema "Karteneditor". =Origin, Set as Origin= :Startpunkt einer Route bei der Berechnung auf der Live-Map. =Pacman Roads, Pacman Straßen= :Unbestätigte Straßen mit kleinen Punkten (Cookies) darauf. Jede unbestätigte Straße der Base-Map, Straßen, die im Waze Map-Editor neu erstellt wurden und noch nicht befahren resp. bestätigt wurden. Werden diese Straßen befahren, ändert sich das Waze-Icon auf dem Display in einen Pacman, der die Punkte frisst. Dafür gibt es Punkte. =Permalink= :Unter [[WME_Oberfläche_und_Steuerelemente#Die_Permalink-Schaltfl.C3.A4che|Permalink]] (früher auch Super-Permalink genannt) versteht man die Funktion einen Link zu generieren, in dem man aktuelle Kartenausschnitte im Waze Map-Editor speichern kann. Der Permalink speichert Informationen wie Koordinaten, ausgewählte Segmente (Straßen) und andere Objekte auf der Karte. Alle Objekte müssen vorgängig per Klick ausgewählt werden, bevor man auf die Permalink-Schaltfläche klickt. Der Permalink entsteht in der Adresszeile Deines Browsers, diesen kannst Du dann kopieren und z.B. für Fragen im Forum verwenden. =Penalty-System= :Für die Erstellung einer Route verwendet Waze auch ein System von Penalties (Zeitzuschläge). Das [[Wie_Waze_Routen_kalkuliert#Penalty-System | Penalty-System]] ist dafür verantwortlich, den schnellsten Weg zu finden. Es eliminiert mögliche Routen, indem es für die Berechnung mehr Zeit (pro Segment oder Kreuzung) vergibt als erwartet. =PM= :''Private Message'' - Eine persönliche Nachricht im Forum die Du an einen anderen Nutzer schicken kannst. Du musst dazu angemeldet sein. =QW= :Mit diesem Kürzel ist das aufeinanderfolgende Drücken der Tasten Q und W gemeint. Wird diese Tastenfolge bei einem markierten Kreuzung (Node) gedrückt, werden alle Abbiegevorschriften an dieser Kreuzung zurückgesetzt. Konkret werden alle sichtbaren Pfeile auf grün gesetzt, und die nicht sichtbaren (beispielsweise entgegen der Fahrtrichtung eines angrenzenden Einbahn-Segments) auf rot gelassen. Die Tastenkombination ist somit ein probates Mittel gegen [[Glossar#Reverse_Connectivity_.2F_RevCon|Reverse Connectivity]]. =Ramp= :Dies sind Ein- und Ausfahrten bei Autobahnen und Schnellstraßen. =Registrierter Benutzer= :Ein registrierter Benutzer hat bereits ein Waze-Konto erstellt. Unregistrierte Benutzer erkennt man auf dem World-Server am Namen der mit '''"world_"''' beginnt =Reverse Connectivity / RevCon= : Eine Reverse Connectivity - auch Reverse Connection genannt, und häufig RevCon abgekürzt - liegt vor, wenn eine erlaubte Verbindung zwischen zwei Segmenten (grüner Pfeil) entgegen der erlaubten Fahrtrichtung eines der Segmente verläuft. Beispiel: Fahrt entgegen einer Einbahnstraße. Dies kann Unregelmäßigkeiten bei der Routenberechnung hervorrufen. :Wie entsteht so etwas? Nehmen wir als Beispiel diese beiden ganz normal verbundenen Zweibahn-Segmente. Vom linken zum rechten Segment zeigt ein grüner Pfeil: :[[Image:RevCon1.png]] :Wird nun das rechte Segment in eine Einbahn mit Fahrtrichtung nach links umgewandelt, wird dieser grüne Pfeil nicht mehr angezeigt, da er ja keinen Sinn mehr macht: :[[Image:RevCon2.png]] :Im Datenbestand ist der grüne Pfeil entgegen die Fahrtrichtung des Einbahn-Segments aber noch vorhanden, und kann die o.g. Unregelmäßigkeiten hervorrufen. =Segment oder Segmente= :Sind die Straßen auf der Karte oder einen Abschnitt im Straßensystem. [[Erstellen und bearbeiten eines Segments | Segmente]] werden durch Kreuzungen verbunden. Segmente sind alle Straßentypen in Waze. =Self Connectivity, SelfCon= :Ein Segment, das in der Waze Datenbank definiert wird, als eine Verbindung durch eine Kreuzung und zurück zu sich selbst. Dies kann Unregelmäßigkeiten bei der Routenberechnung hervorrufen. =Server (Intl. ROW, ROTW, World)= :Damit ist der Internationale [[Die Server Bänke | Server]] gemeint. (ROTW bedeutet: '''R'''est '''O'''f '''T'''he '''W'''orld) =Server (WWW, NA, US)= :Damit ist der Server für die USA/Nordamerika gemeint. =Server (IL)= :Damit ist der Israelische Server gemeint. =Soft-Turns= :[[Soft_und_Hard_Turns|Soft-Turns]] sind Abbiege-Regeln, die vom System automatisch gesetzt wurden. Sie entstehen, wenn mit Waze die Straßen befahren werden. =Support= :Abgesehen von der wörtlichen Übersetzung nennen wir so den Staff (die Mitarbeiter) bei Waze, der Dir bei Problemen hilft und das ganze Waze-Land (Karten, App, etc.) betreut und weiter entwickelt. Im Blog sind einige Mitarbeiter von Waze vorgestellt. =TTS= :''Text-to-speech'' - Gesprochene Navigationsanweisungen in der Waze-App. Es werden Richtungen und Straßennamen gesprochen. =UR= :''Update Request'' - Ein User hat mit der App eine Meldung über Kartenfehler gesendet. =Waze Champs= :Die Devs ernennen besonders aktive und erfahrene Wazer zu Waze Champs. Sie haben Moderatorenrechte im Forum und sind das Bindeglied zwischen der Community und den Devs. =Wazer= :Ein Waze-Benutzer, der mit der App herumfährt, die Karte bearbeitet oder sich sonstwie in die Waze-Gemeinschaft einbringt. =WME= :''Waze Map-Editor'' - Der Karteneditor oder die Browser-Anwendung mit dem man die Waze-Karte bearbeitet. Der interne Codename für WME ist Papyrus. Wir reden aber generell von WME =world_xt6gkd69, usa_xt6gkd69= :Dies sind zufällig generierte Benutzer-Konten. Alle Benutzer, die sich noch nicht mit einer gültigen E-Mail-Adresse registriert haben. Die Registrierung kann auf der Waze Web-Site oder mit der Waze-App erledigt werden. <br> '''Anmerkung:''' Alle Begriffe die hier erläutert werden, tauchen im Wiki oder im Forum auf und begleiten uns auf unserer Odyssee durch das Waze-Land. Hier in der [[Anleitung_zum_Bearbeiten_der_Karte|Anleitung]] findest Du alle weiteren wichtigen Fakten zu diesen Begriffen. Diskutiere auch mit uns im [[Diskussionsforum]], wenn Dir etwas nicht klar ist. ''Siehe auch: [[Glossary|das englische Glossar]]'' <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 434d80b9d7ceb19b3e19a9552ab5b60068294e00 0 102 12035 2017-10-29T21:42:06Z Popel22 24 Die Seite wurde neu angelegt: «'''In Bearbeitung '''<br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Waze has a strong commitment to protecting your privacy and anonymity. =…» wikitext text/x-wiki '''In Bearbeitung '''<br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Waze has a strong commitment to protecting your privacy and anonymity. ==Privacy options in the client app== By default, Waze is configured to keep your details private. This protection is not perfect due to privacy leakage. The [[User_Manual#Privacy_Menu|User Manual]] explains the configuration settings for privacy. ==Privacy Leakage== Privacy leakage is the disclosure and linking of personal information to an apparently anonymous profile. Privacy leakage is not unique to Waze. In fact Waze has very good privacy settings and policies. But they are not perfect, and some problems are inherent to any internet connected service that may contain location information, including Facebook, Twitter, Foursquare and your photos (which may be geotagged). The fact that Waze supports all these options compounds the problem. This list of ways you can lose your privacy is intended to be complete, but there may be other ways not yet recorded. ===Driving location=== Waze is configured by default to display your location as an anonymous driver. To add to your privacy, the location display is delayed, so the location given is where you were 2 minutes earlier. The location of [[Glossary|wazers]] is publicly available to other wazers and on the internet. Rather than being anonymous, you can choose to have your location associated with your nickname. Even when your location is displayed anonymously, there can be privacy leakage. On long highways, isolated country roads, or when traveling at a distance from your home, even anonymous location can disclose your identity. It is possible to identify you from your driving location or driving patterns, especially when combined with an identifying nickname, or other location databases. If you arrive at home and leave Waze on, it will show you in your driveway or home. This may be enough to locate your street address. Public databases such as local government (county) tax and rating records and phone books can be used with an address to find a full name and other personal information. And if a [[glossary|wazer]] comes close enough to see your car and its [[glossary|license plate]], that car registration information can be used to collect personal information and identify you. ===Nickname and Username=== When you first install Waze you are given a random user name. If you change this user name, you may provide additional information about your identity. A first name may be enough to identify you if people observe you regularly driving to the same company location, or to the same street address. Having your company name as part of your nickname may help identify you. Using the same nickname as you use on other social networks like Twitter or Facebook may help identify you. Making a forum post using your nickname where you mention your real name or other personal information may help identify you. This personal information can then be linked to your Waze nickname and Waze identity. The same issues apply to your username which is used on the Waze website, including [[Waze Map Editor]] and [[Discussion Forums]]. Your choice of username and nickname may make it easy to link the two. ===Twitter=== You can choose to link your Waze account to Twitter. By default this will post your road reports to Twitter. You can also choose to tweet your destination, ETA and road munching reports. All of these will disclose your location and movements. By default Twitter accounts are open to the public, and not just your followers. Your Twitter profile may include personal information which can be linked to you and your Waze identity. ===[[Facebook]]=== You can choose to link your Waze account to Facebook. By default this will show your Facebook profile picture to everyone. Facial recognition can be used to identify you. You may choose to disclose your name from Facebook (which is supposed to be your real name). You can also choose to update Facebook with your destination, ETA and road munching reports. All of these will disclose your location and movements. Your Facebook profile may contain more information that allows you to be identified and that information linked to your Waze identity. ===Foursquare=== You can choose to link your Waze account to Foursquare. If you then choose Report/Check in with Foursquare, then Foursquare will disclose your location. Your settings on Foursquare may be linked to other networks such as Facebook and Twitter and update those as well. Your Foursquare image and profile and links to other social networks may allow you to be identified and that information linked to your Waze identity. ===Waze Groups=== You may not link to Twitter or Facebook, but you may be a member of a Waze group. Some of these groups are linked to Twitter. You make a traffic report which is shared with the group, and the group automatically sends it to Twitter and Facebook. Your Waze username (not your nickname) is published in the group membership list, together with the date you joined. This makes it very easy to link your Waze nickname with your Waze username, and reveals information about your probable location and interests. If you do not choose to be anonymous, your icon displayed on the map to other wazers includes an icon badge representing your main group, which can make it easier to identify you amongst the group members. ===Automatic road reports=== A series of reports makes it much easier to identify a [[glossary|wazer]] living or working at a nearby location. It is important to turn off Waze when you have finished traveling, and not just put it in the background. This still remains a problem, as such false reports can be generated just by starting Waze to plan a route before departing. This also means the social part of the social GPS (chit chat) cannot be used from a stationary location without both disclosing your location, and generating false traffic congestion reports. ===Manual [[Road reports]] and [[Chit chat]]=== These reports disclose your Waze nickname, your location, and possibly direction of travel. Making a road report or [[Chit chat]] where you mention your real name or other personal information may help identify you. If you choose to publish road reports to Twitter, your nickname can be linked to your Twitter profile. [[Chit chat]] is considered to be a road report for the purposes of publishing to Twitter and Facebook. By default, road reports are sent to Twitter when you link Waze to your Twitter account. [[Road reports]] may also be sent as a Facebook update if you link Waze to Facebook, but the default setting is not to send to Facebook. A combination of your Facebook or Twitter profile, and your nickname [[Chit chat]] may help disclose personal information about you. ===Creation and editing of roads=== When you [[recording a new road|record a new road]] or edit the layout or details of an existing road, your Waze username is linked to that road. It is natural to edit roads around your home, work, and along your common routes. This may make it easier to identify you and link a Waze nickname commonly traveling on roads created or edited by a Waze nickname. Other map edits such as adding [[house numbers]] are recorded with your Waze username and may make it easier to identify you. ===[[Discussion Forums]]=== Discussion forum posts are made using your username. If you disclose your real name or other personal information in a forum post, this can be linked to your Waze username. ==Practical considerations== ===Using Waze adds an insignificant amount of risk in day to day use=== * Most of us are not going to be the target of stalkers * Owning a [[client device|smartphone]] running Waze does not mean our home is much more likely to be filled with valuable possessions. Running Waze does mean mean that your are more likely to have home security. But thieves may come to different conclusions * Most homes are empty while people are at work from 9am until 5pm. Thieves don't need Waze to know that * Waze by itself doesn't disclose if you are home alone, or if your home is empty * There are easier ways for thieves to find out which houses to rob ===But be sensible=== * Don't [[Chit chat]] saying your whole family is away for 3 weeks leaving the house empty. You might [[Chit chat]] about how you forgot to feed your dog and you hope it doesn't attack anyone * Don't [[Chit chat]] about anything that makes you a target. For example, no [[Chit chat]] about how you hope your jewelery collection is safe in your wardrobe <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] e4318d18597ba199c34a0f82e59d05e42111def0 0 103 12036 2017-10-29T21:42:34Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Waze Anwendung verfügt über eine Anzahl von speziellen Codes, die den Betrieb der Anwendung a…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Waze Anwendung verfügt über eine Anzahl von speziellen Codes, die den Betrieb der Anwendung auf verschielche Funktion sie ausführeedene Weise ändern. Die nachfolgende Tabelle zeigt die derzeit bekannten Codes und wn. Bei einigen dieser Codes ist nicht bekannt, was sie genau bewirken, sie sind deshalb mit "Nicht empfohlen" gekennzeichnet. Die Verwendung dieser Codes sollte nur auf Anordnung des Waze-Supports oder der Waze Champs geschehen. Um einen Code einzugeben, öffne das Hauptmenü in Waze. Wähle ''Navigieren'' und gib den Code in das Suchfeld ein. Einige Funktionen erfordern einen Neustart von Waze, andere wirken sich sofort auf den Betrieb aus. {| class="wikitable sortable" border="1" |+ Bekannte Codes |- ! Code ! Beschreibung ! scope="col" class="unsortable" | Weitere Informationen |- style="background:#99FF99; color:black" | 2##2 || Aktiviert/deaktiviert Debug-Protokollierung || [[Der Debug Mode | Debug Modus einschalten]] |- style="background:#FBEC5D; color:black" | ##@il || Wechselt zur Israel Infrastruktur || Wenn Dein Smartphone mit dem falschen Server verbunden ist, kannst Du mit diesem Code in diese Infrastruktur wechseln. |- style="background:#FBEC5D; color:black" | ##@usa || Wechselt zur US Infrastruktur || Wenn Dein Smartphone mit dem falschen Server verbunden ist, kannst Du mit diesem Code in diese Infrastruktur wechseln. |- style="background:#FBEC5D; color:black" | ##@other || Wechselt zur ROTW Infrastruktur || Wenn Dein Smartphone mit dem falschen Server verbunden ist kannst Du mit diesem Code in diese Infrastruktur wechseln. |- style="background:#FF6666; color:black" | ##@stg || Unbekannt || Nicht empfohlen. Eine Meldung erscheint über eine Änderung der Infrastruktur und fordert zu einem Neustart auf. Nach dem Neustart erscheint die Meldung wieder und der Client schaltet sich aus. Eine Neuinstallation ist erforderlich, um das Problem zu beheben. |- style="background:#FF6666; color:black" | #test# || Unbekannt || Nicht empfohlen. Unbekannte Funktion. |- style="background:#99FF99; color:black" | cc@tts || Bereinigt den TTS-Cache || Wenn TTS nicht korrekt arbeitet, kann es nützlich sein den Cache zu leeren und dadurch einen erneuten Download vom Server zu erzwingen. Dies kann allfällige Ungereimtheiten beseitigen. |- style="background:#99FF99; color:black" | dbg@tts || aktiviert/deaktiviert TTS debugging || |- style="background:#99FF99; color:black" | ##@tts || TTS aktivieren/deaktivieren || Aktiviert oder deaktiviert TTS. Kann auch im Menü Optionen -> Ton eingestellt werden. |- style="background:#99FF99; color:black" | ##@asr || ASR aktivieren/deaktivieren || Aktiviert oder deaktiviert ASR (Automatic Speech Recognition) Sprachbefehle. |- style="background:#FF6666; color:black" | ##@debugtools || Aktiviert oder deaktiviert "alternate debugging" || Nicht empfohlen. Wenn dies eingeschaltet wird, läuft der Client nur noch sehr langsam. |- style="background:#FF6666; color:black" | ##@shift || Aktiviert/deaktiviert "coordinate shift".... || Unbekannt |- style="background:#FF6666; color:black" | ##@enc || Unbekannt || Nicht empfohlen. Suche läuft leer und es passiert nichts. |- style="background:#FF6666; color:black" | ##@map || Unbekannt || Nicht empfohlen. Suche läuft leer und es passiert nichts. |- style="background:#FF6666; color:black" | ## || Unbekannt || Nicht empfohlen. Könnte keinen Suchcode darstellen. |- style="background:#FF6666; color:black" | ##@ || Unbekannt || Nicht empfohlen. Könnte keinen Suchcode darstellen. |- style="background:#99FF99; color:black" | ##@eng || Englisch einstellen || Ändert die Sprache zu Englisch. |- style="background:#99FF99; color:black" | ##@heb || Hebräisch einstellen || Ändert die Sprache zu Hebräisch. |- style="background:#99FF99; color:black" | ##@restorefav || Favoriten wiederherstellen || Lädt die Favoriten vom Server herunter. |- style="background:#99FF99; color:black" | ##@coord || Koordinaten zeigen/verbergen || Zeigt/verbirgt Deine GPS-Koordinaten. |- |} <br> {| class="wikitable unsortable" border="1" |+ Legend |- style="background:#99FF99; color:black" | Falls nötig benutzen |- style="background:#FBEC5D; color:black" | Benutzen mit Vorsicht und nur auf Anweisung |- style="background:#FF6666; color:black" | Nicht benutzen, außer auf spezielle Anweisung |- |} <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] f6b7ff6210fbe302d079f3ba18fd3d5d04e903e1 0 2 12039 11902 2017-10-29T21:45:12Z Popel22 24 wikitext text/x-wiki * [[Diskussionsforum]] * [[Der Waze Chat]] * [[Straßen Berichte]] * [[Facebook]] * [http://www.waze.com/blog/ Waze Blog] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 301e21e5d68567c40a639aa7c26c7a7ac342efa6 12040 12039 2017-10-29T21:46:20Z Popel22 24 wikitext text/x-wiki * [[Diskussionsforum]] * [[Der Waze Chat]] * [[Straßen Berichte]] * [http://www.waze-switzerland.ch/ inoffizielle schweizer Homepage] * [[Facebook]] * [http://www.waze.com/blog/ Waze Blog] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 1ee46eb149ca09ca63f7f52feef43b822edb56cd 12041 12040 2017-10-29T21:46:35Z Popel22 24 wikitext text/x-wiki * [[Diskussionsforum]] * [[Der Waze Chat]] * [http://www.waze-switzerland.ch/ inoffizielle schweizer Homepage] * [[Facebook]] * [http://www.waze.com/blog/ Waze Blog] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] f1d1dbae7f9dd120a88f447b35a722a42a8530dc 0 104 12043 2017-10-29T21:47:31Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =RSS Feeds für das Waze Forum= Um einen bestimmten Feed zu abonnieren, musst Du die Forum-ID hera…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =RSS Feeds für das Waze Forum= Um einen bestimmten Feed zu abonnieren, musst Du die Forum-ID herausfinden, welche zu dem Teil der URL im Forum gehört. Die Forum-ID steht hinter dem "=" Zeichen. Wenn man ein Forum abonniert werden auch alle Unterforen abonniert. Beispiel: *Das "Map" Forum hat die Nummer 8, wie man in der Adresse <span style="color:blue;">viewforum.php?f=8</span> erkennen kann. * Will man nur das "Map" Forum sehen abonniert man folgende Adresse: http://www.waze.com/WAS/forum_feeds?ids=8 * Um ein anderes hinzuzufügen z.B. "Community" (ID=12) kann man einfach die Nummer getrennt durch ein Komma hinzufügen: http://www.waze.com/WAS/forum_feeds?ids=8,12 (ohne Abstände) * Standardmässig werden die letzten 10 Posts angezeigt. Die Anzeige kann aber auch mit &limit=xxx am Ende auf maximal 100 erweitert werden: http://www.waze.com/WAS/forum_feeds?ids=8,54&limit=100 Hier geht's zur [[Feed List|Feed List]] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 445f9f9c983930c275b03a79d397e45ebbf8c522 0 105 12044 2017-10-29T21:48:06Z Popel22 24 Die Seite wurde neu angelegt: «[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Liste der Foren= ===Announcements and Updates = 18=== ===Client = 3=== * User Live Reports and Ro…» wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Liste der Foren= ===Announcements and Updates = 18=== ===Client = 3=== * User Live Reports and Road Validation = 4 * Search = 5 * Navigation = 6 * General Options and Usability = 7 ===Map = 8=== * View and Search = 9 * Editing = 10 * Update requests = 199 * General Options and Usability = 11 * Help When Waze Won't Route to my Destination = 142 * Help When Waze Doesn't Show Alternative Routes to my Destination = 144 ===Community = 12=== * Newcomers and General Discussion = 13 * Permissions, Ranks and Points = 14 ===General 15=== * Thoughts and Suggestions = 16 * Bugs = 17 ==Country (Language) Forums = 19== ===<span style="color:blue;">Latin America Forums = 67 </span>=== ===<span style="color:blue;">Australia = 56 </span>=== ===<span style="color:blue;">Austria & Germany [Deutsch] = 24</span>=== ====Allgemein = 74==== ====Handy-Software = 75==== *WindowsMobile = 82 *IPhone = 83 *Android = 84 *Symbian = 85 *BlackBerry = 118 ====Map-Editor (Cartouch)= 76==== ====Regionen in Deutschland = 77==== * Baden-Württemberg = 89 * Bayern = 90 * Berlin = 91 * Brandenburg = 92 * Bremen = 93 * Hamburg = 94 * Hessen = 95 * Mecklenburg-Vorpommern = 96 * Niedersachsen = 97 * Nordrhein-Westfalen = 98 * Rheinland-Pfalz = 99 * Saarland = 100 * Sachsen = 101 * Sachsen-Anhalt = 102 * Schleswig-Holstein = 103 * Thüringen = 104 ====Regionen in Österreich = 107==== * Burgenland & Niederösterreich = 173 * Kärnten & Steiermark = 174 * Oberösterreich & Salzburg = 175 * Tirol & Vorarlberg = 176 * Wien = 177 * Namen für Straßen, Orte, Landmarks, Gewässer = 178 * Österreichweite Topics = 179 * Tipps & Tricks, damit's funktioniert = 180 * Plauderecke = 78 * Map-Editor (Papyrus) = 197 ===<span style="color:blue;">Belgium = 149</span>=== ===<span style="color:blue;">Caledonie = 196</span>=== ===<span style="color:blue;">Canada = 57</span>=== ===<span style="color:blue;">Catalunya (Catalan) = 159</span>=== ===<span style="color:blue;">Czech Republic and Slovakia = 22</span>=== *CZ: Žádosti o úpravu cest v ČR = 274 *SK: Žiadosti o úpravu ciest na Slovensku = 275 *SK, CZ: Stretnutia Wazerov = 292 ===<span style="color:blue;">Denmark [dansk] = 121</span>=== ===<span style="color:blue;">Finland = 116</span>=== ===<span style="color:blue;">France [Français] = 34</span>=== ====Nouveau ? Besoin d'aide ? Venez ici en premier ! = 194==== * Tutos et astuces = 216 * F.A.Q. = 217 ====Édition de la carte = 68==== * Aide à l'édition = 218 * Les éditeurs, parlons-en ... = 219 * Bugs = 71 ====L’application sur votre smartphone = 69==== * Android = 220 * iOS = 221 * Les autres (désolé) = 222 * Bugs = 223 ====Communauté - Les régions = 70==== * NORD = 228 * EST = 229 * OUEST = 230 * ÎLE-DE-FRANCE = 231 * CENTRE = 232 * SUD-OUEST = 234 * SUD-EST = 235 * D.O.M. = 236 ====Traductions = 106==== ====Pour parler d'autre chose = 224==== ====Archives = 225==== ===<span style="color:blue;">Greece [ελληνικά] = 147</span>=== ===<span style="color:blue;">Hong Kong = 146</span>=== ===<span style="color:blue;">Hungary [magyar] = 25</span>=== * Kliensek = 160 * Cartouche/Régiók = 161 * Szabályok = 162 * Szavazások = 163 * Egyéb felvetések = 164 * Népszerűsítés = 165 * OFFtopik = 166 ===<span style="color:blue;">India = 171</span>=== ===<span style="color:blue;">Indonesia = 154</span>=== ===<span style="color:blue;">Ireland = 119</span>=== ===<span style="color:blue;">Italy = 20</span>=== * Editor: parliamo dell'editor delle mappa "cartouche" = 28 * Client: il nostro navigatore sul telefono = 29 * Community: (no Off-Topic) = 30 * Tutorial/FAQ: (solo lettura) = 31 ===<span style="color:blue;">Isle of Man = 189</span>=== ===<span style="color:blue;">Japan　日本語で。 = 72</span>=== * Kawagoe/Fujimino/Saitama city areas = 172 ===<span style="color:blue;">Kuwait = 187</span>=== ===<span style="color:blue;">Latvia = 151</span>=== ===<span style="color:blue;">Lithuania = 58</span>=== ===<span style="color:blue;">Malaysia = 148</span>=== ===<span style="color:blue;">The Netherlands = 21</span>=== ===<span style="color:blue;">New Zealand = 122</span>=== ===<span style="color:blue;">Norway = 54</span>=== ===<span style="color:blue;">Poland = 73</span>=== ===<span style="color:blue;">Português - Brazil & Portugal = 59</span>=== * Brazil Forum = 60 * Portugal Forum = 61 ===<span style="color:blue;">Qatar (English) = 181</span>=== ===<span style="color:blue;">Spain [Español] = 26</span>=== * Comunidades Autónomas de España = 52 * Edición de mapas = 206 * Funcionamiento en el cliente = 207 * Dudas generales = 208 * Bugs / Reclamos / Quejas = 209 ===<span style="color:blue;">Romania [română] = 120</span>=== ===<span style="color:blue;">Russia [русский язык] = 23</span>=== ===<span style="color:blue;">Serbia [српски] = 117</span>=== ===<span style="color:blue;">Singapore =191</span>=== ===<span style="color:blue;">Slovenia [Slovenski] = 169</span>=== ===<span style="color:blue;">South Africa = 62</span>=== * Gauteng = 131 * Western Cape = 132 * Kwazulu-Natal = 133 * Eastern Cape = 134 * Free state = 135 * Northern Cape = 136 * Limpopo = 137 * Mpumalanga = 138 * North-West = 139 * National roads (N-route numbers) = 140 * Standards = 141 ===<span style="color:blue;">Sweden [svenska] = 33</span>=== ===<span style="color:blue;">Switzerland = 63</span>=== ===<span style="color:blue;">Thailand = 168</span>=== ===<span style="color:blue;">Trinidad and Tobago = 195</span>=== ===<span style="color:blue;">Turkey = 198</span>=== ===<span style="color:blue;">Ukrainian (Українська) = 170</span>=== ===<span style="color:blue;">United Arab Emirates = 150</span>=== ===<span style="color:blue;">United Kingdom = 55</span>=== ===<span style="color:blue;">United States = 129</span>=== * Florida = 193 * Washington = 201 * Tennessee = 210 * Alabama = 213 * Georgia = 214 * Tri-State Region (PA, DE & NJ) = 215 * Texas = 234 * Gulf Coast (LA, MS, AL, FL) = 239 <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 2f6e64210d733ca72b2cae731aafaf102d2d388d 0 4 12046 10249 2017-11-15T06:41:14Z Gbuergisser 37 Rechtschreibung korrigiert wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Karte von Waze ist besonders aktuell. Kartenbearbeitung ist jederzeit im Waze Map Editor (WME) möglich, und in kurzen Abständen wird der aktuelle Stand von Waze in das Navigationssystem übernommen. Waze strebt an, diese Aktualisierung täglich durchzuführen. Dabei wird der Kartenstand zu einem bestimmten Zeitpunkt kopiert, für die Navigation umgerechnet und dann auf den Routingserver übertragen. Dieser Ablauf dauert etwas weniger als einen Tag. Durch den einmal täglich startenden Verarbeitungslauf und die etwa einen Tag dauernde Verarbeitung sind bei optimalem Betrieb die Kartenänderungen am übernächsten Tag auf dem Routingserver angekommen. * Informiere dich hier: [http://status.waze.com Die offizielle Waze Status Seite] bevor Du reklamierst. ==Karten-Aktualisierung== Wenn die App gestartet wird und eine Route berechnet, werden die für die Anzeige nötigen Kartenteile (Kacheln, ca 1kmx1km groß) vom Server geladen. Die App lädt dabei immer die nächsten Streckenabschnitte im Voraus, um auch bei kurzen Funklöchern noch einwandfrei zu funktionieren. Um Datenübertragung zu sparen, werden die Kartendaten einige Tage in der App zwischengespeichert (gecached). Deshalb können nach dem App-Start ohne Navigation auch gelegentlich Kartendaten angezeigt werden die schon einige Tage alt sind. Wenn man mit laufender Routennavigation fährt ist sichergestellt, dass alle Kartendaten entlang der Strecke aktuell sind. ==Verkehrsmeldungen== Verkehrsmeldungen werden in Echtzeit an die Waze-App auf deinem Smartphone gesendet. Dazu gehören Geschwindigkeiten des Verkehrs und Unfallberichte. Die App lädt diese Daten während der Fahrt im Abstand von wenigen Minuten vom Server. ==Aktualisierungsanfragen (Update Requests)== Aktualisierungsanfragen erscheinen im Karteneditor in Echtzeit. ==Die Karte bearbeiten mit WME== Wenn Du nicht [[Der Area Manager|Area Manager]] bist, kannst du nur innerhalb einer Meile oder innerhalb von 1.6 Kilometern um die befahrenen Straßen herum die Karte mit dem Karteneditor(WME) bearbeiten. Die Rechte, um im besagten Radius zu arbeiten sind nicht sofort vorhanden. Normalerweise sind diese spätestens 2 Tage nach dem Erscheinen der gefahrenen Strecken im [[Mein Dashboard|Dashboard]] vorhanden. ==Deine Routen== Wenn Du mit Waze herum fährst, werden deine gefahrenen Strecken im [[Mein Dashboard|Dashboard]] gespeichert. Das letzte Aktualisierungsdatum der Routen steht unten. Im Karteneditor sind die Daten im Reiter "Fahrten" mit Datum/Zeit und Länge/Zeit der gefahrenen Strecke abrufbar. In der Regel sind die gefahrenen Strecken - seit der neue Merger Prozess initialisiert wurde - innerhalb weniger Stunden im Dashboard und Reiter "Fahrten" des Karteneditors ersichtlich. Falls dem nicht so ist, gibt es wichtigere Probleme, die Waze zu der Zeit lösen muss. ==Neu aufgezeichnete Straßen== Wenn Du [[Zeichne Straße auf|neue Straßen aufzeichnest]] werden sie als rote Linien in der App angezeigt, Im [[Der Waze Map-Editor|Karteneditor]] sind diese erst zu sehen, wenn sie auch im [[Mein Dashboard|Dashboard]] resp. im Reiter "Fahrten" des Karteneditors zu sehen sind. Wenn die Straße im [[Der Waze Map-Editor|Karteneditor]] bearbeitet wurde und ein Karten-Update von Waze gemacht wurde, erscheint sie auch in der App und in der [https://www.waze.com/de/livemap/ Live Map]. Die Frist bis diese Straße erscheint liegt bei 2-5 Tagen. Wenn Waze Probleme (Server, Software..) hat, kann es um Einiges länger dauern (bis zu 2-3 Wochen). Wenn die Live-Map aktualisiert wurde, kann es noch einen Tag dauern bis der Routing-Server Deine Straße korrekt behandelt. Du kannst diese Straße in der App sehen und als Ziel annavigieren, aber als Standort in der Suche erscheint sie nicht. In diesem Fall, ist das Routing schlecht oder schlägt fehl. Nun, auch wenn wir manchmal lange warten müssen, die Aktualisierung ist vielfach schneller als bei den meisten anderen GPS-basierten Anwendungen. ==Punkte== Allgemein: Punkte erscheinen nie unmittelbar nachdem man sie erhalten hat in der Statistik. Wenn die [[client device|Anwendung]] sich mit Waze verbindet, erhält sie die angezeigten Punkte von der Waze Statistik. Da Du mit Fahren und anderen Tätigkeiten unterwegs Punkte sammelst, werden diese Punkte von der Waze Anwendung an den Server gesendet. Der Server erhält diese zurück und aktualisiert sie einmal am Tag in der Punktestatistik. Die [[client device|Anwendung]] zeigt dir deine Punkte an, die du erhältst. Sie zeigt aber auch jene an, die dir nicht angerechnet werden. Zum Beispiel, Du erhältst Punkte für das Bestätigen neuer Straßen (sogen. Pacman-Straßen) in dem Du die neuen Straßen mit den kleinen Punkten befährst. Tust Du das, so verwandelt sich Dein Standort-Cursor in ein Waze-Pacman und er beginnt die kleinen Punkte zu fressen. Aber Achtung, es kann aber auch sein, dass jemand eine Stunde vor Dir das gleiche gemacht und die neue Straße schon befahren und dadurch bestätigt hat. Da es die Punkte nur für den Ersten gibt, der eine neue Straße befährt, erhält er folglich auch diese Punkte und nicht du. Der Server wird dein Fahrt dann aussortier und bei der Punktevergabe nicht weiter berücksichtigen. Wenn Du Waze unterwegs neustartest, werden die aktuellen Punkte wieder von der Statistik des Servers heruntergeladen, allerdings ohne die Punkte, die Du für das vermeintliche Fressen der kleinen Punkte auf der neuen Straße gesehen hast. Am Ende des Tages werden alle Punkte auf dem Waze-Server aktualisiert und die Summe der Punkte ist so, wie es sein sollte. ==Punkte fressen(Munching/Pacman-Roads)== Auch wenn Deine gefahrenen Strecken im [[Mein Dashboard|Dashboard]] zu sehen sind, kann eine von dir bestätigte neue Straße immer noch als Pacman-Straße auf der Karte in der App erscheinen. Bis diese als normale Straße erscheint, kann es 2-7 Tage dauern. ==Städte Namen und Grenzen== Auf dem Waze Map-Editor sieht man die Städte mit farbigen Flächen hinterlegt. Diese farbigen Flächen werden durch die Benennung (City Namen) der Straßen definiert. Die Grenzen werden innerhalb von ein paar Tagen aktualisiert. Der Name der Stadt wird in der Mitte erscheinen. Der Name ist nicht immer da wo er sein sollte, dies hängt ab von der Zoom-Stufe und dem aktuellen Ort der Karte, den man anschaut. Bewegt man die Karte auf dem Display wandert auch der Name herum oder verschwindet teilweise ganz. Wird eine einzige Straße mit einem Stadtnamen belegt, liegt der Name auf diesem Segment in der Karte. Je mehr Straßen einem Stadtnamen zugeordnet werden, desto mehr Fläche hat auch der Namen, um sich auf der Karte zu bewegen. ==Automatische Straßen Updates von Waze== Je mehr Wazer (Waze-Benutzer) die Straßen befahren, desto mehr lernt Waze daraus. Waze verändert unbestätigte Straßen in der Geometrie und der Fahrtrichtung. Das Straßenbild verändert sich dadurch dynamisch, z.B. Straßen, sie ändern sich so von zwei- auf einspurig. Darüberhinaus lernt Waze, welche Abbiegungen erlaubt sind wenn die Wazer die Kreuzungen und Abbiegungen befahren. Bei Fehlern, z.B. aufgrund schlechtem GPS-Signals (speziell in Städten), falscher Abbiegungen oder des Befahrens von einspurigen Straßen in falscher Richtung ist Waze sehr konservativ, was diese Änderungen anbelangt. Für das Auslösen von automatischen Korrekturen bzw. Änderungen braucht es zwischen 20 und 100 Fahrten, bevor diese erkannt und korrigiert werden. Dieser Prozess befindet sich im stetigen Wandel. * Lese im [http://world.waze.com/forum/ Forum] nach. * Benutze die [http://www.waze.com/forum/search.php Foren Such-Funktion] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] a1362b97c64dab2136771bde82645938a77670f3 12057 12046 2018-05-14T21:01:36Z Popel22 24 /* Automatische Straßen Updates von Waze */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Die Karte von Waze ist besonders aktuell. Kartenbearbeitung ist jederzeit im Waze Map Editor (WME) möglich, und in kurzen Abständen wird der aktuelle Stand von Waze in das Navigationssystem übernommen. Waze strebt an, diese Aktualisierung täglich durchzuführen. Dabei wird der Kartenstand zu einem bestimmten Zeitpunkt kopiert, für die Navigation umgerechnet und dann auf den Routingserver übertragen. Dieser Ablauf dauert etwas weniger als einen Tag. Durch den einmal täglich startenden Verarbeitungslauf und die etwa einen Tag dauernde Verarbeitung sind bei optimalem Betrieb die Kartenänderungen am übernächsten Tag auf dem Routingserver angekommen. * Informiere dich hier: [http://status.waze.com Die offizielle Waze Status Seite] bevor Du reklamierst. ==Karten-Aktualisierung== Wenn die App gestartet wird und eine Route berechnet, werden die für die Anzeige nötigen Kartenteile (Kacheln, ca 1kmx1km groß) vom Server geladen. Die App lädt dabei immer die nächsten Streckenabschnitte im Voraus, um auch bei kurzen Funklöchern noch einwandfrei zu funktionieren. Um Datenübertragung zu sparen, werden die Kartendaten einige Tage in der App zwischengespeichert (gecached). Deshalb können nach dem App-Start ohne Navigation auch gelegentlich Kartendaten angezeigt werden die schon einige Tage alt sind. Wenn man mit laufender Routennavigation fährt ist sichergestellt, dass alle Kartendaten entlang der Strecke aktuell sind. ==Verkehrsmeldungen== Verkehrsmeldungen werden in Echtzeit an die Waze-App auf deinem Smartphone gesendet. Dazu gehören Geschwindigkeiten des Verkehrs und Unfallberichte. Die App lädt diese Daten während der Fahrt im Abstand von wenigen Minuten vom Server. ==Aktualisierungsanfragen (Update Requests)== Aktualisierungsanfragen erscheinen im Karteneditor in Echtzeit. ==Die Karte bearbeiten mit WME== Wenn Du nicht [[Der Area Manager|Area Manager]] bist, kannst du nur innerhalb einer Meile oder innerhalb von 1.6 Kilometern um die befahrenen Straßen herum die Karte mit dem Karteneditor(WME) bearbeiten. Die Rechte, um im besagten Radius zu arbeiten sind nicht sofort vorhanden. Normalerweise sind diese spätestens 2 Tage nach dem Erscheinen der gefahrenen Strecken im [[Mein Dashboard|Dashboard]] vorhanden. ==Deine Routen== Wenn Du mit Waze herum fährst, werden deine gefahrenen Strecken im [[Mein Dashboard|Dashboard]] gespeichert. Das letzte Aktualisierungsdatum der Routen steht unten. Im Karteneditor sind die Daten im Reiter "Fahrten" mit Datum/Zeit und Länge/Zeit der gefahrenen Strecke abrufbar. In der Regel sind die gefahrenen Strecken - seit der neue Merger Prozess initialisiert wurde - innerhalb weniger Stunden im Dashboard und Reiter "Fahrten" des Karteneditors ersichtlich. Falls dem nicht so ist, gibt es wichtigere Probleme, die Waze zu der Zeit lösen muss. ==Neu aufgezeichnete Straßen== Wenn Du [[Zeichne Straße auf|neue Straßen aufzeichnest]] werden sie als rote Linien in der App angezeigt, Im [[Der Waze Map-Editor|Karteneditor]] sind diese erst zu sehen, wenn sie auch im [[Mein Dashboard|Dashboard]] resp. im Reiter "Fahrten" des Karteneditors zu sehen sind. Wenn die Straße im [[Der Waze Map-Editor|Karteneditor]] bearbeitet wurde und ein Karten-Update von Waze gemacht wurde, erscheint sie auch in der App und in der [https://www.waze.com/de/livemap/ Live Map]. Die Frist bis diese Straße erscheint liegt bei 2-5 Tagen. Wenn Waze Probleme (Server, Software..) hat, kann es um Einiges länger dauern (bis zu 2-3 Wochen). Wenn die Live-Map aktualisiert wurde, kann es noch einen Tag dauern bis der Routing-Server Deine Straße korrekt behandelt. Du kannst diese Straße in der App sehen und als Ziel annavigieren, aber als Standort in der Suche erscheint sie nicht. In diesem Fall, ist das Routing schlecht oder schlägt fehl. Nun, auch wenn wir manchmal lange warten müssen, die Aktualisierung ist vielfach schneller als bei den meisten anderen GPS-basierten Anwendungen. ==Punkte== Allgemein: Punkte erscheinen nie unmittelbar nachdem man sie erhalten hat in der Statistik. Wenn die [[client device|Anwendung]] sich mit Waze verbindet, erhält sie die angezeigten Punkte von der Waze Statistik. Da Du mit Fahren und anderen Tätigkeiten unterwegs Punkte sammelst, werden diese Punkte von der Waze Anwendung an den Server gesendet. Der Server erhält diese zurück und aktualisiert sie einmal am Tag in der Punktestatistik. Die [[client device|Anwendung]] zeigt dir deine Punkte an, die du erhältst. Sie zeigt aber auch jene an, die dir nicht angerechnet werden. Zum Beispiel, Du erhältst Punkte für das Bestätigen neuer Straßen (sogen. Pacman-Straßen) in dem Du die neuen Straßen mit den kleinen Punkten befährst. Tust Du das, so verwandelt sich Dein Standort-Cursor in ein Waze-Pacman und er beginnt die kleinen Punkte zu fressen. Aber Achtung, es kann aber auch sein, dass jemand eine Stunde vor Dir das gleiche gemacht und die neue Straße schon befahren und dadurch bestätigt hat. Da es die Punkte nur für den Ersten gibt, der eine neue Straße befährt, erhält er folglich auch diese Punkte und nicht du. Der Server wird dein Fahrt dann aussortier und bei der Punktevergabe nicht weiter berücksichtigen. Wenn Du Waze unterwegs neustartest, werden die aktuellen Punkte wieder von der Statistik des Servers heruntergeladen, allerdings ohne die Punkte, die Du für das vermeintliche Fressen der kleinen Punkte auf der neuen Straße gesehen hast. Am Ende des Tages werden alle Punkte auf dem Waze-Server aktualisiert und die Summe der Punkte ist so, wie es sein sollte. ==Punkte fressen(Munching/Pacman-Roads)== Auch wenn Deine gefahrenen Strecken im [[Mein Dashboard|Dashboard]] zu sehen sind, kann eine von dir bestätigte neue Straße immer noch als Pacman-Straße auf der Karte in der App erscheinen. Bis diese als normale Straße erscheint, kann es 2-7 Tage dauern. ==Städte Namen und Grenzen== Auf dem Waze Map-Editor sieht man die Städte mit farbigen Flächen hinterlegt. Diese farbigen Flächen werden durch die Benennung (City Namen) der Straßen definiert. Die Grenzen werden innerhalb von ein paar Tagen aktualisiert. Der Name der Stadt wird in der Mitte erscheinen. Der Name ist nicht immer da wo er sein sollte, dies hängt ab von der Zoom-Stufe und dem aktuellen Ort der Karte, den man anschaut. Bewegt man die Karte auf dem Display wandert auch der Name herum oder verschwindet teilweise ganz. Wird eine einzige Straße mit einem Stadtnamen belegt, liegt der Name auf diesem Segment in der Karte. Je mehr Straßen einem Stadtnamen zugeordnet werden, desto mehr Fläche hat auch der Namen, um sich auf der Karte zu bewegen. * Lese im [http://world.waze.com/forum/ Forum] nach. * Benutze die [http://www.waze.com/forum/search.php Foren Such-Funktion] <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] fc297af63bba009a49138abc2f8360f043d8a924 0 10 12047 10649 2017-12-05T22:37:47Z Popel22 24 /* Strassen */ 4x4 / Feldwege gelöscht wikitext text/x-wiki [[Strassen und Orte benennen in der Schweiz|Zurück zu Strassen und Orte benennen in der Schweiz]] ==Segmente und Kreuzungen== [[Image:Segmente und Kreuzungen.png]] '''Was ist ein Segment?''' In der Geometrie eine Linie, die durch zwei Endpunkte begrenzt ist. Im [[Der Waze Map-Editor|Kartenditor]], benützen wir [[Erstellen und bearbeiten eines Segments|Segmente]] um neue Strassen zu zeichnen. Wie oben schon gesagt hat das Segment eine Begrenzung. In unserem Fall ist dies eine [[WME_Schnellstart-Anleitung#Kreuzung_erstellen|Kreuzung]]. * In der Schweiz richtet sich die Klassifizierug nach der Beschilderung. Mehr Informationen zur Benennung und Zuordnung findest Du hier im [[Strassen und Orte benennen in der Schweiz|Wiki Schweiz]] <b>Bitte beachte auch, dass die Klassifizierung von Land zu Land unterschiedlich ist. Deshalb ist es wichtig, bei der Bearbeitung im Ausland die länderspezifischen Wikis zu kennen.</b> ==Segment Typen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "ß" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! ===Fernstrassen=== '''Autobahn [[Image:RoadBlue.png|200px]]''' Als Freeway wird in der Schweiz eine Autobahn mit Richtungsgetrennten Spuren ohne Ampeln und Stoppschilder definiert. Autobahnen sind nur durch Ein- und Ausfahrten zugänglich. Strassen wie, Hauptstrassen, Nebenstrassen etc. können nicht direkt auf eine Autobahn verbunden sein. Ausnahmen bilden Zufahrten für Schutz und Rettung, welche aber für den Pendler nicht navigierbar sein sollen. Viele Nationalstrassen führen über Autobahnen, in all diesen Fällen gelten die Autobahn Bezeichnungen vorrangig. Eine Liste aller Autobahnen in der Schweiz gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] Die Farbe aller Autobahnschilder und Wegweiser in der Schweiz ist grün. [[Image:AutobahnSchild.png‎]] [[Image:AutobahnEnde.png‎]] [[Image:WegweiserAutobahn.png‎]] ---- '''Bundesstraße [[Image:Majorhighwayseg.png |200px]]''' Als Bundesstraße definieren wir alle Schnell- und Autostrassen, die nicht Autobahnen sind. Autostrassen sind in der Schweiz wie Autobahnen - abgesehen von wenigen Autobahnzubringern - immer kreuzungsfrei angelegt, aber im Gegensatz zu Autobahnen selten richtungsgetrennt und meistens einspurig. Eine Liste aller Autostrassen gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] Die Autostrassen sind auch grün ausgeschildert. [[Image:Autostrasse.png]] [[Image:EndeAutostrasse.png]] ---- '''Landesstraße [[Image:RoadYell.png |200px]]''' Als Landesstraße definieren wir alle nummerierten Hauptstrassen und Nationalstrassen in der Schweiz. Die Nummerierung richtet sich nach der Beschilderung. An Ortsausfahrten sind die Nummern unter dem Hauptstrassen- oder Ortsschild ersichtlich. Eine Liste aller Nummerierten Hauptstrassen gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] Eine Liste aller Nationalstrassen gibt es hier: [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] [[Image:NummerierteHauptstrasse.png]] [[Image:HauptstrasseAusserorts.png]] [[Image:WegweiserNummerierteHauptstrasse.png]] ---- '''Rampe [[Image:Ramp.png |200px]]''' Rampe wird für Ein- und Ausfahrten auf Autobahnen verwendet. [[Image:AusfahrtWegweiser.png]] [[Image:Ausfahrtstafel.png]] ---- ===Strassen=== Auch in den Städten finden wir die verschiedensten Strassentypen: ---- '''Hauptstraße [[Image:Primary street.png|200px]]''' Als Hauptstraße ordnen wir alle Strassen nach der Beschilderung. [[Image:Hauptstrasse.png]]‎ [[Image:HauptstrasseEnde.png]] [[Image:HaupstrasseOrtsbeginn.png]] [[Image:HaupstrasseOrtsende.png]] [[Image:WegweiserHauptstrasse.png‎]] ---- '''Straße [[Image:Street.png|200px]]''' Als Straße definieren wir alle Strassen und Nebenstrassen, wie Quartierstrassen oder sonstige, die für den Normalverkehr uneingeschränkt befahrbar sind. Diese können Einbahnstrassen oder auch Strassen mit Gegenverkehr sein. Nebenstrassen sind weiss ausgeschildert. Sie werden auch auf Landstrassen verwendet. [[Image:NebenstrasseOrtsbeginn.png]] [[Image:Nebenstrasse Ortsende.png]] [[Image:WegweiserNebenstrasse.png‎]] Normale Strasse: [[Image:RoadPicN4.jpg|400px]] ---- '''Zufahrtsstraße [[Image:Service road.png|200px]]''' Zufartsstraßen werden nicht verwendet. ---- '''Parkplatz [[Image:Service road.png|200px]]''' Als Parkplatz definieren wir grosse Parkplätze, Parkplätze innerhalb Raststätten, Strassen an Parkplätze oder Siedlungen mit Parkplätzen. [[Image:RoadPicN7.jpg |400px]] ---- '''Privatstraße [[Image:Service road.png|200px]]''' Als Privatstraße werden alle Strassen definiert, die auch so bezeichnet oder beschildert sind. Ferner sind sie zu verwenden, wo ein Routing ausgeschlossen werden soll für den Normalverkehr (Zubringerdienst etc.). Lies dazu das Thema [[Fußwege und Privatstraßen]]. ---- '''Fußweg [[Image:Service road.png|200px]]''' Als Fußweg sind alle Fusswege zu definieren. '''Alle Fusswege dürfen keine Verbindung zwischen zwei routbaren Strassen besitzen.''' Lies dazu das Thema [[Fußwege und Privatstraßen]]. [[Image:RoadPicN9.jpg |400px]] ---- '''Fußgängerzone[[Image:Service road.png|200px]]''' Als Fußgängerzone definieren wir Fussgängerzonen, Uferwege. '''Alle Fusswege dürfen keine Verbindung zwischen zwei routbaren Strassen besitzen.''' [[Image:RoadPicN10.jpg|400px]] ---- '''Treppe [[Image:Service road.png|200px]]''' Als Treppe sind alle Treppenwege zu bezeichnen. '''Alle Fusswege dürfen keine Verbindung zwischen zwei routbaren Strassen besitzen.''' [[Image:RoadPicN11.jpg|400px]] ---- '''Eisenbahn [[Image:Service road.png|200px]]''' Als Eisenbahn sind die Eisenbahnlinien zu definieren. Diese sind in der App jedoch nicht sichtbar. Sie sollen auch nicht über die App aufgezeichnet werden, sondern im Waze Map-Editor hinzugefügt werden. Sie müssen auch mit Level -5 versehen werden und dürfen keine Verbindungen auf bestehende Strassen aufweisen. Die Benennung richtet sich nach dem Namen der Bahn. ---- '''Landebahn [[Image:Service road.png|200px]]''' Als Landebahn können Lande- und Rollbahnen eingezeichnet werden (Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten und jeden Weg darauf einzuzeichnen, Orientierungspunkt (Flughafen) reicht vollkommen aus!) Wieder: keine Verbindung zum normalen Strassennetz! <br> [[Strassen und Orte benennen in der Schweiz|Zurück zu Strassen und Orte benennen in der Schweiz]] [[Category:Schweiz]] ff4ba1baf6e33aaa947ab128e87e125d42ee5a93 0 77 12048 11946 2017-12-14T09:48:53Z Vince1612 23 wikitext text/x-wiki ===== <big>'''Les règles de fermetures des signalements d'erreurs de carte (''UR - "User Report"'') en Suisse sont les suivantes:'''</big> ===== '''Solved (corrigé)''' * Si '''vous pouvez''' '''identifier clairement la raison du signalement''' <u>et</u> que '''vous êtes capable de corriger le problème dans l'éditeur''', que '''vous parvenez à faire la modification''' <u>et</u> sauvegardez celle-ci correctement. Alors '''à ce moment vous pouvez marquer l'UR comme "corrigé"'''. Sinon, veuillez toujours fermer comme ci-dessous: <br> '''Not identified (non identifié)''' * Si pour plusieurs raisons, comme le manque de détails ou des conflits entre le tracé GPS et la route suggérée, vous ne parvenez pas à trouver la raison du signalement. Dans ces cas là, vous devriez tenter d'entrer en communication avec l'auteur du signalement. * Si une conversation a déjà été initiée par un autre éditeur et qu'un temps raisonnable a passé depuis les dernières informations fournies par l'auteur du signalement, vous pouvez laisser un message pour suggérer que l'UR soit fermé. Il est préférable d'attendre une réaction de l'autre éditeur avant de prendre action vous-même sur l'UR. * Si vous ne recevez pas de réponse dans un délai raisonnable après avoir posé des questions vous pouvez considérer l'option de fermer l'UR en non identifié.<br>Mais aussi, parfois des utilisateurs signalent des problèmes valides, mais qui ne peuvent pas être corrigés dans l'éditeur de carte. Ces signalement devraient eux-aussi être fermés comme non identifiés, avec une explication à l'auteur du signalement que le problème signalé ne peut pas ou ne sera pas corrigé dans l'éditeur. <br> '''Merci donc à tous de ne fermer les UR comme corrigé que si toutes les conditions citées ci-dessus sont remplies, et <u>ceci peu importe si la discussion dans le chat de l'UR a apporté une réponse ou une solution mais qu'aucune modification de carte n'a été effectuée.</u>''' ====== <br> <big>'''Pourquoi insister là-dessus?'''</big> ====== Outre le fait que de noter un UR comme corrigé sans avoir fait de modifications ou de corrections n'est pas approprié, vous devez prendre en compte que l'auteur de l'UR reçoit lui aussi des notifications du système immédiatement après une fermeture de son signalement. Un exemple de mail reçu lorsque l'UR est fermé comme corrigé: <br><blockquote><small>''Hi vince1612, <br><br><span style="color:#0000FF">The map issue you reported</span> from 11.09.2016 on Álafossvegur, Mosfellsbær ("Dead end. Concrete blocks blocking the road") <span style="color:#0000FF">was fixed by tbk0</span>. <br><span style="color:#0000FF">The map has been updated accordingly</span>. You've helped many wazers. Thanks!<br><br><span style="color:#0000FF">You can see the fixed area in the Waze map editor here</span> <nowiki>https://www.waze.com/editor/?zoom=5&lat</nowiki> ... 28&env=row''</small></blockquote><br><br>Essentiellement si on informe un utilisateur via le chat que son problème ne sera pas corrigé ou ne pourra pas l'être, ou même que l'on réponde à sa question mais toujours sans modifier la carte. Il est très <u>contradictoire</u> qu'il reçoive directement par la suite un message l'informant: * Que le problème qu'il a signalé a été résolu - <span style="color:red">faux</span> * Que la carte a été mise à jour - <span style="color:red">faux</span> * Qu'il a aidé beaucoup de Wazer et qu'il est remercié - c'est l'intention qui compte, mais <span style="color:red">faux</span> * Qu'il peut voir les corrections faites dans l'éditeur avec le permalink fourni - <span style="color:red">archi-faux</span> <br>D'autant plus que ceci est aussi ce qu'il reçoit sur son application en plus de l'e-mail. ===== Note sur le signalement "Mauvais sens de circulation" ===== En cas d'UR comprenant le titre ci-dessus, veuillez considérer la chose suivante: Le texte d'origine de ce signalement est "Wrong driving direction", ceci a causé pas mal de confusion lors de la traduction car en anglais le mot "direction" peut autant signifier '<nowiki/>''sens'' de circulation' qu'il peut signifier '''instruction'' de navigation ou de conduite'. Suivant la langue dans laquelle le Wazer utilise l'application Waze, il peut donc soit vouloir signaler une erreur dans le sens de circulation, soit vouloir signaler qu'il a reçu de mauvaises instructions de navigation/guidage pour une étape de son parcours ou pour sa destination finale. Il convient donc dans ces cas là d'entamer une discussion dans l'UR et de demander des précisions. Seul moyen de pouvoir être sûr. a393956295c4c1c06bdafc247e0007b79082e4f7 0 76 12049 11935 2018-01-15T09:30:59Z Vince1612 23 wikitext text/x-wiki [[Datei:Virages difficiles.jpeg|mini|Virages difficiles]] '''Sur l'application''' Allez dans Réglages - Navigation et vous remarquerez le nouveau réglage vous permettant d'indiquer à Waze si vous préférez éviter les virages difficiles ou non. '''Sur WME''' Waze ne décide pas automatiquement quels virages sont difficiles, il appartient à la communauté locale de les indiquer comme tels dans WME. Cette fonction est disponible via le même menu que les restrictions de circulation pour les flèches d'autorisation de tourner et est activable via une case à cocher, tout simplement. Cette fonction n'est modifiable sur l'éditeur que pour ceux ayant atteint le niveau 2. Si le segment est verrouillé à un niveau supérieur il sera toujours nécessaire de demander un déverrouillage. '''Effets et recommandations''' Marquer un virage comme difficile le pénalisera 24/24h et 7/7j - Il n'est pas possible ou prévu pour l'instant de pouvoir régler des jours ou horaires particuliers. Merci donc de bien vouloir observer ces quelques indications: * Cette fonction a été créée à la base pour des carrefours sans feux et lorsque tourner à droite est simple, mais que de traverser ou de tourner à gauche peut être très difficile à réaliser en raison du trafic prioritaire (voir illustration ci-dessus). Chaque Wazer peut ensuite décider ou nom via le réglage de l'application s'il souhaite que Waze les évites ou non. * Le réglage a été activé par défaut pour tout le monde - À noter donc que tout ajout de virage difficile impactera 95% des utilisateurs en supposant que seuls 5% auront remarqué l'apparition ce nouveau réglage et éventuellement choisi de le désactiver. * Merci de n'appliquer cette pénalité que lorsque cela vous semble vraiment nécessaire, car en raison de l'effet permanent et de l'activation par défaut, ce même virage sera également pénalisé en cas de faible trafic routier ou durant la nuit, ce qui pourrait causer une certaine incompréhension chez certains Wazers. * Merci de ne pas utiliser cette fonction sur des carrefours équipés de feux de signalisation (même si le rouge est "très long").<br>L'algorithme chargé de calculer la vitesse moyenne de temps de passage sur le segment de A à B devrait en principe déjà prendre en compte un temps de passage plus long et s'adapter aux conditions du trafic en se basant sur es données historiques et en temps réel. Ce qui est préférable à un effet négatif permanent. 43da42ec0de641433e2100989b3527ac2473f13e 12052 12049 2018-03-20T14:43:15Z Vince1612 23 wikitext text/x-wiki [[Datei:Virages difficiles.jpeg|mini|Virages difficiles]] '''Sur l'application''' Allez dans Réglages - Navigation et vous remarquerez le nouveau réglage vous permettant d'indiquer à Waze si vous préférez éviter les virages difficiles ou non. '''Sur WME''' Waze ne décide pas automatiquement quels virages sont difficiles, il appartient à la communauté locale de les indiquer comme tels dans WME. Cette fonction est disponible via le même menu que les restrictions pour les flèches d'autorisation de tourner et est activable via une case à cocher, tout simplement. Cette fonction n'est modifiable sur l'éditeur que pour ceux ayant atteint le niveau 2. Si le segment est verrouillé à un niveau supérieur il sera toujours nécessaire de demander un déverrouillage. '''Effets et recommandations''' Marquer un virage comme difficile le pénalisera selon les réglages jours/horaires définis. On pourra donc par exemple pénaliser un certain tournant en permanence, seulement en semaine et/ou uniquement durant certaines tranches horaires. '''Merci de bien vouloir observer ces quelques indications:''' * Cette fonction a été créée à la base <u>pour des carrefours sans feux</u> et lorsque tourner à droite est simple, mais que de traverser ou de tourner à gauche peut être très difficile à réaliser en raison du trafic prioritaire (voir illustration ci-dessus). Chaque Wazer peut ensuite décider ou nom via le réglage de l'application s'il souhaite que Waze les évites ou non. * Le réglage a été activé par défaut pour tout le monde - À noter donc que tout ajout de virage difficile impactera 95% des utilisateurs en supposant que seuls 5% auront remarqué l'apparition ce nouveau réglage et éventuellement choisi de le désactiver. * Merci de n'appliquer cette pénalité que lorsque cela vous semble vraiment nécessaire, en cas de doute, il est recommandé d'ouvrir une discussion sur le forum et de demander l'avis d'autres éditeurs ou des AM/CM connaissant la zone. * <u>Merci de ne pas utiliser cette fonction sur des carrefours équipés de feux</u> de signalisation (même si le rouge est "très long").<br>L'algorithme chargé de calculer la vitesse moyenne de temps de passage sur le segment de A à B devrait en principe déjà prendre en compte un temps de passage plus long et s'adapter aux conditions du trafic en se basant sur es données historiques et en temps réel. * Cet outil ne doit pas être utilisé à des fins personnelles pour influencer négativement un itinéraire que l'on aime pas. cc86cc6e4aaa5397583edc2fa36025922262cf86 12053 12052 2018-03-20T14:50:43Z Vince1612 23 wikitext text/x-wiki [[Datei:Virages difficiles.jpeg|mini|Virages difficiles]] '''Sur l'application''' Allez dans Réglages - Navigation et vous remarquerez le nouveau réglage vous permettant d'indiquer à Waze si vous préférez éviter les virages difficiles ou non. '''Sur WME''' Waze ne décide pas automatiquement quels virages sont difficiles, il appartient à la communauté locale de les indiquer comme tels dans WME. Cette fonction est disponible via le même menu que les restrictions pour les flèches d'autorisation de tourner et est activable via une case à cocher, tout simplement. Cette fonction n'est modifiable sur l'éditeur que pour ceux ayant atteint le niveau 2. Si le segment est verrouillé à un niveau supérieur il sera toujours nécessaire de demander un déverrouillage. '''Effets et recommandations''' Marquer un virage comme difficile le pénalisera selon les réglages jours/horaires définis. On pourra donc par exemple pénaliser un certain tournant en permanence, seulement en semaine et/ou uniquement durant certaines tranches horaires. '''Merci de bien vouloir observer ces quelques indications:''' * Cette fonction a été créée à la base <u>pour des carrefours sans feux</u> et lorsque tourner à droite est simple, mais que de traverser ou de tourner à gauche peut être très difficile à réaliser en raison du trafic prioritaire (''voir illustration ci-dessus''). Chaque Wazer peut ensuite décider ou nom via le réglage de l'application s'il souhaite que Waze les évites ou non. * Le réglage a été activé par défaut pour tout le monde - À noter donc que tout ajout de virage difficile impactera 95% des utilisateurs en supposant que seuls 5% auront remarqué l'apparition ce nouveau réglage et éventuellement choisi de le désactiver. * Cet outil ne doit pas être utilisé à des fins personnelles pour influencer négativement un itinéraire que l'on aime pas. Merci de n'appliquer cette pénalité que lorsque cela vous semble vraiment nécessaire, en cas de doute, il est recommandé d'ouvrir une discussion sur le forum et de demander l'avis d'autres éditeurs ou des AM/CM connaissant la zone. * <u>Merci de ne pas utiliser cette fonction sur des carrefours équipés de feux</u> de signalisation (même si le rouge est "très long").<br>L'algorithme chargé de calculer la vitesse moyenne de temps de passage sur le segment de A à B devrait en principe déjà prendre en compte un temps de passage plus long et s'adapter aux conditions du trafic en se basant sur es données historiques et en temps réel. a67bd21df3657c79ea13bb9844faaeef4ea41915 0 12 12050 11901 2018-01-28T15:07:33Z Vince1612 23 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1 (inaktiv)||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | svx-biker||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} 66d444daba9344631255777479c2383358b90b5a 12051 12050 2018-01-28T15:08:18Z Vince1612 23 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1 (inaktiv)||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |} 949a90b97d7ffada2f46b38c6685e76f65a4c9c3 12054 12051 2018-05-14T20:54:40Z Popel22 24 /* Deutschland */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1 (inaktiv)||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |- | | | | | | | | | |} 908b687a58c9c58a1475fc532393bf78ca3068f3 12055 12054 2018-05-14T20:56:47Z Popel22 24 /* Verwendete Abkürzungen */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1 (inaktiv)||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=273942 PM]''</span> |- | | | | | | | | | |} e99c62d64765b3d84c1526f75afb19bafcb35a41 12056 12055 2018-05-14T20:58:13Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | Raccoon_1 (inaktiv)||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||E||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>|| |- | | | | | | | | | |} 4bd7cda4d1eaad2cf821bacc0c431c4612e8434f 12064 12056 2018-06-17T20:47:17Z Popel22 24 /* Deutschland */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | ''Raccoon_1 (inaktiv)''||''5''||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||x||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||X||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||E||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>|| |- | | | | | | | | | |} 260a33b445136341fcce8ef0b8975f3f576ec3d4 12065 12064 2018-08-31T21:46:36Z Popel22 24 /* Österreich */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | ''Raccoon_1 (inaktiv)''||''5''||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||x||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||E||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||E||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>|| |- | | | | | | | | | |} 0ada643cdf6742b4fe602c047a3d52a4b1dc7a1a 12069 12065 2019-06-01T20:42:53Z Vince1612 23 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | ''Raccoon_1 (inaktiv)''||''5''||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Österreich == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | caradellino||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6883842 PM] |- | TSWA||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1218624 PM] |- | beffl||6||||x||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8206602 PM] |- | AlexN-114||5||||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=8262764 PM] |- | GPSRitter||5||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=7528576 PM] |- | omba_de||5||||E||||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5763955 PM] |- | GangMan||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=976644 PM] |- | ghost012||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=9361264 PM] |- | stefan147||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10217429 PM] |- | fuchserl||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16827143 PM] |- | pmex||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16887707 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||E||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>|| |- | | | | | | | | | |} 8823347bf112042c79b18507f89f174c20757b18 0 7 12058 11992 2018-05-14T21:23:43Z Popel22 24 /* Nicht befahrbare */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ==== '''Unterschied zwischen Fussweg und Fussgängerzone:''' ==== PB are ignored for routing, the navigation will guide the Wazer to the nearest drivable segmentregardless of any PB which may be mapped closer to the destination. WT, if connected to a drivable road AND being the closest segment to a destination, Waze navigation guides the Wazer to the closest node where the WT is connected to a drivable segment, where the Wazer should basically park and continue on foot. ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Eisenbahnlinien können bei niveaugleichen Bahnübergängen mit anderen Strassen verbunden werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 2 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 43011ca4fae7d732f81ea90d749eb9ec3b4503bb 12059 12058 2018-05-14T21:33:11Z Popel22 24 /* Unterschied zwischen Fussweg und Fussgängerzone: */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ==== '''Unterschied zwischen Fussweg und Fussgängerzone:''' ==== <nowiki>https://wazeopedia.waze.com/wiki/Commons/images/8/8d/WTvsPB.png</nowiki> PB are ignored for routing, the navigation will guide the Wazer to the nearest drivable segmentregardless of any PB which may be mapped closer to the destination. WT, if connected to a drivable road AND being the closest segment to a destination, Waze navigation guides the Wazer to the closest node where the WT is connected to a drivable segment, where the Wazer should basically park and continue on foot. ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Eisenbahnlinien können bei niveaugleichen Bahnübergängen mit anderen Strassen verbunden werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 2 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] db44bdeb3464613c56c5c2ea3c51c155f98168df 12060 12059 2018-05-14T21:36:46Z Popel22 24 /* Unterschied zwischen Fussweg und Fussgängerzone: */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ==== '''Unterschied zwischen Fussweg und Fussgängerzone:''' ==== <code>[[File:</code><nowiki>https://wazeopedia.waze.com/wiki/Commons/images/8/8d/WTvsPB.png</nowiki><code>]]</code> PB are ignored for routing, the navigation will guide the Wazer to the nearest drivable segmentregardless of any PB which may be mapped closer to the destination. WT, if connected to a drivable road AND being the closest segment to a destination, Waze navigation guides the Wazer to the closest node where the WT is connected to a drivable segment, where the Wazer should basically park and continue on foot. ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Eisenbahnlinien können bei niveaugleichen Bahnübergängen mit anderen Strassen verbunden werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 2 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 5104b717655faf84b2d68067a2a7f42f4579a102 12061 12060 2018-05-14T21:38:34Z Popel22 24 /* Unterschied zwischen Fussweg und Fussgängerzone: */ wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ==== '''Unterschied zwischen Fussweg und Fussgängerzone:''' ==== PB are ignored for routing, the navigation will guide the Wazer to the nearest drivable segmentregardless of any PB which may be mapped closer to the destination. WT, if connected to a drivable road AND being the closest segment to a destination, Waze navigation guides the Wazer to the closest node where the WT is connected to a drivable segment, where the Wazer should basically park and continue on foot. ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Eisenbahnlinien können bei niveaugleichen Bahnübergängen mit anderen Strassen verbunden werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 2 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 51a97423ea1d8d495a589ff41863e5f0a6ac5c5b 12062 12061 2018-05-14T21:38:55Z Popel22 24 wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Feldweg/4x4 Weg'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ==== '''Unterschied zwischen Fussweg und Fussgängerzone:''' ==== [[File:WTvsPB.png]] PB are ignored for routing, the navigation will guide the Wazer to the nearest drivable segmentregardless of any PB which may be mapped closer to the destination. WT, if connected to a drivable road AND being the closest segment to a destination, Waze navigation guides the Wazer to the closest node where the WT is connected to a drivable segment, where the Wazer should basically park and continue on foot. ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Eisenbahnlinien können bei niveaugleichen Bahnübergängen mit anderen Strassen verbunden werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 2 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] a85e5f82b82de4a171409b9740faa99837bfd2cc 12073 12062 2019-07-09T09:37:48Z Popel22 24 wikitext text/x-wiki [[Switzerland|Zurück zum Wiki Schweiz]] =Strassen Zuordnung= Hier findest Du die Zuordnung und Benennung für die Strassen und Orte in der Schweiz. * Bei Fragen beteilige dich hier im [http://www.waze.com/forum/viewtopic.php?f=63&t=3608 Diskussions-Thread]. * Lies diese Seite über die Verwendung [[Der_Waze_Map-Editor#Einsatz_von_externen_Quellen_.28wie_Google_Imagery.29|externer Quellen]]. Waze ist nicht OSM, frage uns im Forum, wenn Du dazu Informationen brauchst. =Kartenlegende Schweiz= Hier findest Du die [[Kartenlegende Schweiz]] mit Informationen zur Beschilderung und den einzelnen Segmenten. =Strassen Kategorien= ==Fernstraßen== * <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, und nummerierte Hauptstrassen * <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen ==Straßen== * <span style="color:RoyalBlue;">'''Hauptstraße'''</span> => Hauptstrasse * <span style="color:RoyalBlue;">'''Straße'''</span> => Andere Strassen, Nebenstrassen ==Andere - befahrbare== * <span style="color:RoyalBlue;">'''Offroad'''</span> => Kiesstrassen, Feldstrassen (Land- Forstwitschaft), Waldstrassen etc. die vom Normalverkehr befahren werden dürfen. --> Wird in der Schweiz nur in Ausnahmefällen verwendet * <span style="color:RoyalBlue;">'''Parkplatz'''</span> => Grosse Parkplätze, Strassen an Parkplätze oder Siedlungen mit Parkplätzen * <span style="color:RoyalBlue;">'''Privatstraße'''</span> => Privatstrassen und alles was nicht vom Normalverkehr befahren werden darf. * <span style="color:RoyalBlue;">'''Fähre'''</span> ==Nicht befahrbare== * <span style="color:RoyalBlue;">'''Fußweg'''</span> => Fusswege * <span style="color:RoyalBlue;">'''Fußgängerzone'''</span> => Fussgängerzonen, Uferwege * <span style="color:RoyalBlue;">'''Treppe'''</span> => Treppen * <span style="color:RoyalBlue;">'''Eisenbahn'''</span> => Eisenbahnen * <span style="color:RoyalBlue;">'''Landebahn'''</span> => Lande- und Rollbahnen <br>(Dies ist der Vollständigkeit halber vorhanden hier. Es macht aber keinen Sinn alle Flughäfen damit auszustatten, Landmark (Airport) reicht vollkommen aus!) ==== '''Unterschied zwischen Fussweg und Fussgängerzone:''' ==== [[File:WTvsPB.png]] PB are ignored for routing, the navigation will guide the Wazer to the nearest drivable segmentregardless of any PB which may be mapped closer to the destination. WT, if connected to a drivable road AND being the closest segment to a destination, Waze navigation guides the Wazer to the closest node where the WT is connected to a drivable segment, where the Wazer should basically park and continue on foot. ''' ==Anmerkung zu den Strassentypen== Die Strassentypen, die hier beschrieben werden, lehnen sich an die Deutsche Lokalisierung des Karteneditors an. Diese wird in drei Ländern verwendet, daher sind die Typenbezeichnungen mit "'''ß'''" geschrieben. Alle Strassen in der Schweiz sind nicht mit diesem Sonderzeichen zu versehen, das Wiki Schweiz untersteht der Schweizer Lokalisierung. Strasse schreibt man mit "ss"! Wenn Du die englische Lokalisierung gebrauchen willst, schau die "Main Page" im Wiki an. '''Lies das Thema [[Fußwege und Privatstraßen]].''' =Beschilderung= Zuordnung der Haupt- und Nebenstrassen: * Es ist auf die Beschilderung zu achten. ** Blaue Wegweiser, Ortsschilder, viereckiges Spiegelei (Hauptstrasse) => Hauptstraße ** Weisse Wegweiser, Ortsschilder (Nebenstrasse) => Straße =Strassen benennen= ==Autobahnen== Typ: <span style="color:RoyalBlue;">'''Autobahn'''</span> => Autobahn * Benennung A1, A2, A3 - E60 etc. ==Autostrassen== Typ: <span style="color:RoyalBlue;">'''Bundesstraße'''</span> => Richtungsgetrennte Schnellstrassen, Autostrassen * Benennung A1L, A52 etc. ==Nationalstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" N1, N2 etc. * Ausserorts ohne Strassennamen: N1, N2 etc. Sofern Die Nationalstrasse über eine Autobahn führt mit der Autobahnbezeichnung und dem Eintrag "Alt Street/Alias" N1, N2 etc. ==Nummerierten Hauptstrassen== Typ: <span style="color:RoyalBlue;">'''Landesstraße'''</span> => National-, Hauptstrassen <br> * Benennung Innerorts: Mit Strassennamen und Eintrag "Alt Street/Alias" H1, H2 etc. * Ausserorts, wenn keine Strassennamen vorhanden sind: H1, H2 etc. ==Ein- und Ausfahrten== Typ: <span style="color:RoyalBlue;">'''Rampe'''</span> => Ein- und Ausfahrten auf Autobahnen Benennung nach den Bezeichnungen auf den Schildern der Ein- und Ausfahrten. Die Orte geben dabei gleichzeitig die Richtung an. Um eine Richtungsangabe in Einfahrten zu erzeugen verwendet man das Zeichen ">", welches für "Richtung" steht und auch so gesprochen wird von TTS. Um die Ansagen kurz zu halten, werden keine Europastrassen-Nummern in die Richtungsangaben eingefügt. "/" = 0,25 Sekund Pause im TTS * Ausfahrt 13 > Zürich / Flughafen, Ausfahrt 1 > Bülach-Nord * A1 > Basel / Bern / Luzern, A1 > Zürich / Dietikon *[[Image:AusfahrtWegweiser.png]] Ausfahrt 43 > Niederbipp / Langenthal *[[Image:WegweiserAutobahn.png]] A2 > Basel ===Kreuze Benennen im Karteneditor=== Kreuze und Autobahnanschlüsse sind im Karteneditor mit einem "Orientierungspunkt" zu versehen. Der Orientierungspunkt wird den Ein- und Ausfahrten angepasst und mit dem Namen und der Nummer des Kreuzes versehen. Als Typ des Orientierungspunkts wird "Kreuzung/Autobahnkreuz" ausgewählt. '''Beispiel:''' "17 Frick" *[[Image:Frick.png|600px]] '''Beispiel:''' "8 Liestal" *[[Image:Augst.png|600px]] ==Normale Strassen== Benennung mit Strassennamen nach der Beschilderung, keine Abkürzung der Namen in Str. oder ähnlichem. =Benennung der Orte= Stelle sicher, dass ein Name nur einmal existiert, konsultiere die Ortsliste weiter unten und installiere dazu dieses Script hier: http://userscripts.org/scripts/show/175260. Es zeigt Dir an, wenn sich falsche Orte auf der Karte befinden. Zudem besitzt es diverse Highlight-Funktionen, die Dir das Arbeiten auf der Karte erleichtern. Es sollen nur Ortsnamen erfasst werden, welche eine eigene PLZ haben. Es gibt kein Niemandsland oder Strassen ohne City-Eintrag (Ausnahmen Autobahnen, Ein- und Ausfahrten): Alle Ortsgrenzen sind an die von der Schweiz definierten Grenzen anzupassen. Achtung: Manche Gemeinden haben verschiedene PLZ (Lausanne, Luzern, Zürich, etc.). Grossstädte werden daher trotzdem nicht in Quartiere unterteilt. Der Eintrag im City-Feld erhält lediglich den Stadtnamen. ==Ortsliste Schweiz== Hier findest Du die [[Ortsliste Schweiz]] Verwende nur Orte, die in dieser Liste vorhanden sind! Bei Unklarheiten frage uns im Forum. =Wichtige Infos= ==Waldstrassen== Bei den Waldstrassen ist zu bedenken, dass gewisse nur zu Fuss begehbar sind. ==Eisenbahnen== Eisenbahnen sollten generell nicht aufgezeichnet werden auf dem Client, sondern im Map Editor eingezeichnet werden. Eisenbahnlinien können bei niveaugleichen Bahnübergängen mit anderen Strassen verbunden werden. City-Namen ist leer und wird nicht angegeben. Als Benennung reicht der Name des Betreibers der Bahn. Empfohlen wird auch ein Lock von Level 2 Editoren. ==Fahrspuren== In der Regel gilt für Autobahnen zwei Spuren. Dies erleichtert das Mappen der Ein- und Ausfahrten. * Bei anderen Strassen: Wenn zwischen den Spuren genügend Platz vorhanden ist (gem. Wiki 5 Meter) oder im 100 Meter Zoom im Editor zwei gut erkennbare GPS Punkt Spuren mit genügend Abstand zueinander zu sehen sind, können auch zwei gezeichnet werden. Richtungsgetrennte Schnellstrassen, grössere Hauptstrassen oder sonstige Autostrassen. [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#In_zwei_Einbahnstra.C3.9Fen_aufteilen_oder_nicht.3F|Weitere Infos hier.]] =Quellen= *Liste der Autobahnen gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autobahnen_in_der_Schweiz] *Liste der Autostrassen (Major Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Autostrassen_in_der_Schweiz] *Liste der Nationalstrassen (Freeways/Minor Highways) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Nationalstrassen_der_Schweiz] *Liste der Nummerierten Hauptstrassen (Minor Highway) gibt es hier [http://de.wikipedia.org/wiki/Liste_der_Hauptstrassen_der_Schweiz] <br> [[Switzerland|Zurück zum Wiki Schweiz]] [[Category:Schweiz]] 3434829832e8c4a3d93153732f0146a13eb7c05a 0 5 12063 10367 2018-05-22T21:56:03Z Popel22 24 /* End-Kreuzung */ Teil mit der Endkreuzung gelöscht, da kein Problem mehr wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] == Einleitung == Wie Waze selbst ist diese Seite durch die Gemeinschaft entstanden und entwickelt sich kontinuierlich weiter. Viele hilfreiche Seiten existieren bereits unter [[Der Area Manager]], wie man den [[Der Waze Map-Editor|Karteneditor]] benutzt, Kartenfehler identifiziert und bearbeitet, Standards um Straßen zu klassifizieren und zu benennen und eine Seite über [[Häufig gestellte Fragen]]. Der Zweck dieser Seite ist es, Area-Managern und allen Benutzern zu helfen, eine Karte zu erstellen, welche für alle Waze-Endbenutzer während der Fahrt gut funktioniert. Auch kann so Mehraufwand durch nochmaliges Bearbeiten auf Grund von Fehlern oder Beschränkungen der Waze-Applikation vermieden werden. == Anleitungen == Im Wiki finden sich zahlreiche Anleitungen. Das Wichtigste am Anfang ist daher, sich mit den Anleitungen auseinanderzusetzen. Also lies die [[Anleitung zum Bearbeiten der Karte]] sorgfältig, bevor Du die Karte bearbeitest. == Hauptziele == === Benutzerfreundlichkeit === Wenn es um die Karte geht, ist das oberste Gebot: Für den Waze-Benutzer eine einfache Karte zu erstellen, der einfach zu folgen ist auf dem kleinen Bildschirm. Die Anweisungen sollen klar und sinnvoll sein und nur dann erscheinen, wenn sie auch gebraucht werden. === Einfachheit === Es soll nicht jede einzelne Spur auf der Karte eingezeichnet werden. Dies führt häufig nur zu unnötiger Komplexität, unlogischen Anweisungen beim Navigieren sowie unübersichtlichen Verhältnissen auf der Karte und schlussendlich zu unnötiger Mehrarbeit beim Korrigieren. === Erhaltung des bestehenden Zustandes === Durch das Befahren der Straßen werden in den Segmenten Informationen gespeichert, wie z.B. die Geschwindigkeit, welche für das optimale Routing benötigt wird. Wenn ein Segment gelöscht wird, gehen diese Informationen verloren. Wenn an einem unübersichtlichen Gewirr von Segmenten gearbeitet wird, ist es die bessere Wahl, diese weiterzuverwenden, anstatt bestehende zu löschen und neu zu zeichnen. == In der Praxis == === In zwei Einbahnstraßen aufteilen oder nicht? === Es ist selten eine gute Idee, eine Straße, die nur durch Ein- und Ausfahrten auf eine Autobahn oder Hauptverkehrsstraße verbunden ist, in zwei Einbahnen aufzuteilen. An einer Kreuzung müssen auch nicht die Einmündungen aufgeteilt werden. Kreuzungen werden dadurch unnötig kompliziert, auf dem Bildschirm ist nichts mehr richtig zu erkennen, und die Anweisungen bei der Navigation sind verwirrend oder unsinnig. <br/>'''Eine Straße sollte in zwei Einbahnen aufgeteilt werden wenn:''' *Mindestens 5 Meter Abstand zwischen den Fahrspuren besteht. (Abgetrennt durch Beton, Blumentöpfe oder Beete, Bäume oder Grasflächen.) *Die GPS-Punkte liegen bei einer Zoomstufe von 100 Metern im Karteneditor genügend weit auseinander. <br/>'''Eine Straße sollte nicht in zwei Einbahnen aufgeteilt werden wenn:''' *Eine nicht befahrbare Fläche von weniger als 5 Metern zwischen den Fahrspuren besteht. *Eine längere Abbiegespur zwischen beiden Fahrtrichtungen existiert. *Viele Straßen kreuzen, die nur auf die nächstliegende Fahrbahn führen. *Google Maps oder andere Karten die Straßen so anzeigen. === Wie man zwei Einbahnen zu einer Fahrspur vereint === Wer eine Straße in zwei Fahrspuren aufteilt, sollte auch verstehen, was alles dazugehört, dies rückgängig zu machen. Es gibt leider keinen einfachen Weg zwei getrennte Fahrspuren wieder in eine zweispurige Straße zurückzuwandeln. Deshalb sollte man sich das Aufteilen gut überlegen. Wenn man eine Straße antrifft, die nicht aufgeteilt sein sollte, erkennt man dies sehr gut an der Summe der Fehlermeldungen der User. Dort wo die meisten Meldungen liegen brennt es in der Regel. Danach beginnt die hohe Kunst der Karten-Chirurgie am Waze-Karteneditor. Folgende Schritte sind zu erledigen: #Löschen der einen oder anderen Seite inkl. der Segmente, die beide Straßen verbinden. #Alle verwaisten Kreuzungen entfernen. #Richtungsänderungen an der verbleibenden Straße vornehmen. #Alle Abbiegeverbote kontrollieren. #Verbinden inkl. Abbiegeverbote aller Straßen, die in die verbleibende Straße münden. #Sicherstellen, dass die verleibende Straße korrekt in beide Richtungen verbunden ist. #Die Geometrie der zweispurigen Straße in die Mitte korrigieren. <br/>Damit man sich damit nicht zu viel Arbeit einheimst, sollte man vorher die richtige Straße auswählen, die verbleiben soll. Dies entscheidet man natürlich anhand der bereits verbundenen Segmente. Man kann auch übers Kreuz löschen damit man schneller vorwärts kommt. Nicht vergessen die verbleibende Straße wieder korrekt mit ihr selbst zu verbinden. === Autobahnen und Anschlüsse === Langstrecken-Navigation ist nicht möglich, wenn die Autobahnen nicht korrekt verbunden sind. Deshalb ist diesem Thema besondere Aufmerksamkeit zu widmen. Man kann sehr viel bewirken, wenn man diese korrekt erstellt. Besondere Überlegungen müssen bei eingeschränkt befahrbaren Straßen angestellt werden. Es kann bei unsorgfältiger Vorgehensweise auch mehr Schaden enstehen, als an normalen Quartierstraßen. ==== Straßen ==== Beschränkt zugängliche Straßen mit mehreren Spuren in beiden Richtungen, die durch ein Hindernis zwischen den Spuren abgetrennt sind und allein durch Rampen zugänglich sind, sollten fast immer in zwei Einbahnen aufgeteilt werden. Andere normale Straßen sollten meistens nicht aufgeteilt werden. ==== Ein- und Ausfahrten ==== Einfahrten sollten nach der Richtung in die sie führen benannt werden. Ausfahrten sollten nach der Ausfahrtnummer - wenn vorhanden - und auch der Beschilderung der Ausfahrten benannt werden. Dabei auch gleich die Verbindungen und Abbiegeverbote kontrollieren. *Es gibt in den länderspezifischen Wikis mehr Informationen zur Benennung. *Verstehe den Unterschied zwischen Ein- und Ausfahrten und ebenerdigen [[Abbiegespuren]] ==== Über- und Unterführungen ==== Erfahrungen haben gezeigt, dass es sinvoller ist einzelnen bestimmten Segmenten einen unterschiedlichen Level zu geben, als längeren Straßen die nicht durch Kreuzungen unterteilt sind. Autobahnen beispielsweise sollten generell auf Level 0 bleiben. Brücken die darüber führen Level 1. Über- oder Unterführungen sollten nicht Level 0 haben. Auch bei komplizierten Verzweigungen sollten die Levels den tatsächlichen Zustand widerspiegeln. Trifft man auf Segmente, die bereits im Level verändert wurden, muss man dem Drumherum besondere Aufmerksamkeit schenken, damit nicht fehlerhafte Levels entstehen an Straßen, die bereits korrekt erstellt wurden. In den meisten einfachen Fällen können Probleme beseitigt werden, wenn man den Level eines Segments ändert. Bei komplizierten Kreuzungen kann es hilfreich sein, eine Zeichung zu erstellen oder man schaut sich zuerst die höchst- oder tiefstliegendsten Segmente an, um sich Klarheit zu verschaffen. Gelegentlich kommt man auch an eine Kreuzung, wo die Levels auf den ersten Blick keinen Sinn ergeben. Es kann daher hilfreich sein, ein Segment durch eine Kreuzung zu unterteilen. Es bleibt dann zu hoffen, dass nicht jemand die Kreuzung löscht ohne sich vorher zu vergewissern, wieso die da ist. ==== Ebenen in Straßen ==== Egal welche Ebene eine Straße besitzt, wenn sie durch eine Kreuzung verbunden wird, wird die ganze Verzweigung navigierbar. Wenn man eine Über- oder Unterführung findet, die mit der darüber- oder darunterliegenden Straße durch eine Kreuzung verbunden ist, so ist diese Kreuzung zu löschen. Waze navigiert die Benutzer sonst von einer Brücke auf eine draunterliegende Straße (oder umgekehrt), was nicht sehr sinnvoll ist. Man vergewissert sich dabei zuerst, ob die Ebenen der kreuzenden Straßen und die Benennung der einzelnen Segmente gleich sind. Ansonsten kann die Kreuzung nicht gelöscht werden. Desweiteren kann man dies auch mit der Brücken-Funktion beheben. ==== Brücken-Funktion ==== Zwei Segmente, die über- oder unterführen auswählen und das Brückensymbol anklicken. Die beiden Segmente vereinen sich und der Level erhöht sich automatisch auf Level 1. Falls damit kein Erfolg erzielt wird muss man allf. die Segmente einzeln abtrennen und neu verbinden. Verbindest Du mit der Brücken-Funktion Segmente, die unterschiedliche Levels besitzen, erhöht sich der Level um einen höher, als das Segment mit dem höchsten Level. ==== Für Normalverkehr gesperrt oder zeitlich beschränkte Fahrverbote ==== Inzwischen unterstützt Waze auch [[Straßensperrungen und zeitlich beschränkte Fahrverbote|zeitlich beschränkte Fahrverbote]], Richtungswechsel zu bestimmten Zeiten oder Straßen, die für bestimmte Fahrzeuge reserviert sind. Diese Straßen haben manchmal eigene Einfahrten und führen parallel entlang normaler Straßen. Das Routing kann dadurch Anweisungen geben, die falsch sind oder gar tödlich enden können! Die einfachste Lösung war bisher, diese Straßen zu löschen, falls sie bereits erstellt wurden. Dies ist jedoch nicht erwünscht. Daher ist es sinnvoll, die erweiterten Eigenschaften möglichst überall hinzuzufügen. === Wann sind Ramps an Kreuzungen zu verwenden === Siehe hier [[Abbiegespuren]] === Wann ein Kreisverkehr erstellt werden soll === Wenn klar ist, wie man [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehre]] erstellt, ist es die richtige Zeit alle Kreisel, die nur aus einzelnen Straßen Segmenten gezeichnet wurden auszutauschen und durch richtige Kreisverlehre zu ersetzen. Das gleiche gilt für Kreisverkehre der Basis-Karte (Base Map), die ganz leicht an ihrer seltsam eckigen Form erkannt werden können. Spätestens nach dem Korrigieren wird einem klarwerden, wie die [[Erstellen und bearbeiten eines Kreisverkehrs|korrekten Ansagen]] bei der Navigation zustandekommen. === Richtung und Sperren von Straßen === '''Wozu sperrt man Segmente?''' Die "Sperren"-Funktion bewirkt gem. [[Häufig gestellte Fragen#Was ist eine gesperrte Straße im Waze Map-Editor.3F|den Häufig gestellten Fragen]] folgendes: *Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]]. *Zwingt das Routing, den verbundenen Segmenten zu folgen und macht es nahezu unmöglich, gegen die definierte Fahrtrichtung zu Routen. '''Wann sperrt man Segmente?''' ''[[Wichtig: Unvollständige Segmente werden nicht gesperrt.]]'' Grundsätzlich bleiben Straßen frei. Waze lebt von den Beiträgen vieler, und jeder soll die Möglichkeit behalten, aktuelle Änderungen an Straßen schnell und einfach einzutragen. Sperren sollten also nur auf wichtigen Straßen vorgenommen werden, wo durch die Bearbeitung durch Einsteiger gravierende Auswirkungen, insbesondere auf den überregionalen Verkehr zu befürchten sind. Folgende Straßen müssen gelockt werden, wenn sie vollständig bearbeitet sind: *Autobahnen samt den zugehörigen Auf- und Abfahrten: Level 4 oder 5 *Bundesstraßen: Level 3 Wenn diese Straßen durch einen Editor niedrigen Ranges erstellt oder bearbeitet wurden, fordert er die Sperrung mit dem richtigen Level im Forum an. '''Informiere Dich in den länderspezifischen Wikis über die Gegebenheiten im betreffenden Land!''' === Konnektivität === Nur weil sich zwei Segmente an einer Kreuzung berühren, heißt dies noch nicht, dass sie auch korrekt miteinander verbunden sind. Abbiegeverbote kontrollieren! === Unnötige Kreuzungen === Unnötige Kreuzungen sind zu entfernen, da sie oft zu fehlerhaften Verbindungen und falschen Straßennamen führen. Zudem sind sie für das [[Wie Waze Routen kalkuliert|Routing]] nicht von Vorteil, da pro Kreuzung ein Zuschlag von 5 Sekunden zur Fahrzeitberechnung addiert wird. Ausnahmen bilden Orts- oder Landesgrenzen, oder wenn man in Kürze eine Straße mit einer Kreuzung verbindet. Wenn Kreuzungen entfernt werden, muss darauf geachtet werden, dass die Segmente die gleichen Eigenschaften besitzen. Andernfalls kann die Kreuzung nicht entfernt werden. Kreuzungen auf Straßen mit der Eigenschaft "Unbekannt" können aus Sicherheitsgründen nicht gelöscht werden. Straßen in Richtung ändern und nach dem Entfernen der Kreuzung allf. wieder auf "Unbekannt" setzen. == Neue Straßen == === Aufzeichnen mit der Waze-App === Nach dem Aufzeichnen muss die Straße im Editor bearbeitet werden. Aufgezeichnete und unbearbeitete Straßen tauchen zwar in der App auf, sie werden aber nicht für das Routing benutzt. '''Man sollte diesen Anweisungen folgen:''' #Geometrie ausrichten anhand der Luftaufnahme, sofern diese am richtigen Ort ist in der Gegend. Dies sollte mit der Ebene GPS-Punkte geprüft werden. Kanten und Ecken abrunden wo nötig. #Korrekter Straßentyp und Name anhand der Definition des Landes einfügen. #Die korrekte Fahrtrichtung bestimmen. #Kreuzungen hinzufügen und Straßen korrekt verbinden. <br/>Wenn mit dem Bearbeiten einer neuen Straße (rot) begonnen wird, wird die Straße ohne Typenänderung weiß erscheinen. Nach dem nächsten Kartenupdate von Waze, wird diese dann auf der Echtzeit-Karte und der Waze-App zu sehen sein. Daher ist es nicht sehr hilfreich, eine unfertige Straße zu hinterlassen. Solange sie rot ist, merkt mann noch, dass die Straße bearbeitet werden muss. Aber sobald sie weiß wird, kann sie im Karteneditor nicht mehr so schnell identifiziert werden. Wenn sie nur weiß ist und auch einen Straßennamen hat, mag dies gut aussehen, aber Waze weiß vielleicht noch nicht, dass die Straße befahren werden kann. == Parkings und Parkplätze == Das Zuordnen eines Parkplatzes und dessen Straßen dient zwei Zwecken: *es erlaubt Waze eine Tür-zu-Tür-Navigation innerhalb des Parkplatzes *es erlaubt Waze von einer Hauptstraße weg zu navigieren, um fehlerhafte Verkehrsmeldungen zu vermeiden ==== Gebrauch des "Parkplatz"-Straßentyps ==== "Parkplatz" ermöglicht das Erstellen von Parkplätzen und verhindert gleichzeitig, dass der Routing-Server diese für die Navigation miteinbezieht. Damit nicht durch Parkplätze geroutet wird, hat Waze den Routing-Algorithmus im Juni 2012 geändert. Jedes Segment, das sich innerhalb eines Parkplatzes befindet ist daher als "Parkplatz" zu definieren. ==== Einkaufszentren ==== Wenn ein Parkplatz eines Einkaufszentrums erstellt wird, sollten Haupteinfahrten und die wichtigsten Verbindungen erstellt werden, Verbindungen zwischen verschiedenen Parzellen eines Parkplatzes und entlang der Geschäfte. Die meistgebrauchten Spuren sollten dabei miteinbezogen werden. Am wichtigsten sind hier Benutzerfreundlichkeit und Einfachheit. Es macht keinen Sinn, jedes einzelne Parkfeld mit einem Segment zu bestücken, dies lässt die Karte auf der App nur unübersichtlich aussehen. ==== Kleinere Parkplätze ==== Parkplätze, die einer kleinen Anzahl von Unternehmen dienen, sollten minimal sein. Genug, um dem Fahrer richtige Richtungen, Ein- und Ausfahrten zu zeigen und den Weg zu einem Geschäft. Manchmal reicht ein einziges paralleles Segment. ==== Durchfahrts-Parkplätze ==== Diese sollten nicht zu viele Einbahnen enthalten und am besten mit einer Einbahn als Schlaufe durch den Parkplatz führen. Man bedenke dabei, dass sich eine [[WME Schnellstart-Anleitung#Straßen-Schlaufen|Straße]] nicht mit sich selbst verbindet. ==== Parkhäuser ==== Wenn ein Parkhaus nur eine Ein- und Ausfahrt besitzt, sollte diese mindestens auf der Karte erscheinen. Ein einzelnes zweispuriges Segment reicht aus, da im Parkhaus meistens kein GPS-Signal vorhanden ist. Der Straßentyp ist "Parkplatz" und das Parkhaus kann mit einem Orientierungspunkt versehen werden. Besitzt das Parkhaus separate Ein- und Ausfahrten, so sollte eine Durchfahrt ermöglicht werden. Dazu reicht in den meisten Fällen ein einziges Segment. Es ist nicht nötig, jedes Stockwerk des Parkhauses darzustellen, dies macht die Karte nur unnötig unübersichtlich. == Unterdrücken von Verkehrsmeldungen und Kartenfehlern == Straßensegmente vom Typ "Parkplatzstraße" verhindern die Erstellung von Staumeldungen, und von Kartenfehlern für "fehlende Straße". == Klassifizierung von Kreuzungen == Verschiedene Arten von Kreuzungen haben [[Classification of crossings|Standard-Möglichkeiten]], um diese zu bearbeiten. Interessant sind auch diese Seiten:<br/>[[Kreuzungen]]<br/>[[Abbiegespuren]] <center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br/>[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 49a7b3bf416479d8ece13df174cec52c619d1b81 0 1 12066 12001 2018-10-12T05:50:50Z Gbuergisser 37 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. * '''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone]. Hilfe und Anleitungen findest Du (vorerst nur auf englisch im [https://support.google.com/waze#topic=6273402 Help Center] * '''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] * '''Bitte nicht''' ** an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast ** [[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind ** Strasse und Orte benennen bis Du [[Strassen und Orte benennen in der Schweiz]] gelesen hast * '''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] * '''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: * [[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> * [[Strassen und Orte benennen in der Schweiz]] * [[Kartenlegende Schweiz]] * [[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> * [[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] * [[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> * Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. * Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse * Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] * Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] * Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> * [[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" | [[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 9ad2707e9f049d2d10ae37965d2e800706b2644a 0 78 12067 11998 2018-12-21T22:35:40Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies qui longent les routes autours du parking (pour empêcher les voiture sur le parking d'être collées sur la route avec du trafic par erreur ce qui risquerait de déclencher des signalement de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par un rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 33081d7362d97adc2ceb1a8c21eea72642f7d7bd 12068 12067 2018-12-21T22:39:06Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par un rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. b2524eb09832ee36320ddfa9d0677659cc161ca4 0 85 12070 12010 2019-07-03T19:47:56Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] = Die verschiedenen Stufen = Du kannst Deine eigene [[WME Oberfläche und Steuerelemente#Ich|Stufe]] im Waze Karteneditor oben links unter deinem Benutzernamen einsehen. Die Stufen werden anhand von orangefarbenen Pilonen dargestellt.<br/>Wenn Du eine Straße im Karteneditor auswählst, kannst Du ebenso Deine Stufe einsehen, wenn Du die Straße erstellt, aufgezeichnet oder bearbeitet hast (vorher speichern). Die Stufe steht hinter dem Benutzernamen in Klammern.<br/>Beispiel: Benutzer(0) Wenn Deine Stufe tiefer ist als erwartet - basierend auf den Kriterien, die unten aufgeführt sind (Ersichtlich im [[Mein Dashboard#Your Rank and Points|Dashboard]] unter Map-Updates), melde dies im [[Glossar#DACH|DACH-Raum]] dem Selfmanagement-Team, resp. einem Manager Deines Landes (per [https://www.waze.com/forum/ucp.php?i=pm&mode=compose PM im Forum]). Selfmanagement-Team für alle DACH-Länder: *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *popel22 (CH) *Vince1612 (CH) * {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Level-Tabelle" |- ! Stufe / Pilonen !! Edit-Radius !! Erforderliche Mindest-Edits !! Beschreibung !! Art der Beantragung |- |class="unsortable" align="center" | 1 ||class="unsortable" align="center" | 1,6 km ||class="unsortable" align="center" | 0 || Macht sich mit dem [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] und dem [https://www.waze.com/forum/viewforum.php?f=24 Forum] vertraut. || |- |class="unsortable" align="center" | 2 ||class="unsortable" align="center" | 3,2 km ||class="unsortable" align="center" | 3.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und orientiert sich an den Regeln. Stellt (spätestens jetzt) erste Fragen im [https://www.waze.com/forum/viewforum.php?f=24 Forum], um sich weiter zu verbessern. || Hochstufung erfolgt automatisch |- |class="unsortable" align="center" | 3 ||class="unsortable" align="center" | 4,8 km ||class="unsortable" align="center" | 25.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Ist im [https://www.waze.com/forum/viewforum.php?f=24 Forum] präsent und ist per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 4 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 100.000 || Dieselben Kriterien wie Stufe 3 || PM an Self-Management-Team |- |class="unsortable" align="center" | 5 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 250.000 || Setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um. Ist im Forum aktiv und per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 6 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 500.000 || || PM an Self-Management-Team |} Unabhängig von den Edit-Stufen gibt es die Rollen ''Area Manager (AM)'' sowie ''Country Manager (CM)'': {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Rollen-Tabelle" |- ! Rolle !! Beschreibung !! Art der Beantragung |- | Area Manager (AM) || Steht in seinem AM-Gebiet den Usern unterstützend/beratend zur Seite. Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Lock-Regeln (sprich: er kann nur Segmente bis zu seinem Edit-Level bearbeiten, wie alle). Ein AM hat das Wiki gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Er ist im Forum präsent und per PM erreichbar.|| [[Der_Area_Manager|AM-Formular]] |- |State Manager (SM) |Steht in seinem SM-Gebiet (Kanton) den Usern unterstützend/beratend zur Seite. Sein SM-Gebiet ist immer als ganzes für dem SM zum Bearbeiten freigeschaltet, der SM untersteht aber den normalen Lock-Regeln (sprich: er kann nur Segmente bis zu seinem Edit-Level bearbeiten, wie alle). Ein SM hat das Wiki gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Er ist im Forum präsent und per PM erreichbar. | |- |''RTC State Manager'' |Dies ist eine Spezialrolle, die es bisher nur in der Schweiz gibt. Der ''RTC State Manager'' ist in einem oder mehreren Kantonen für Strassensperrungen zuständig und erhält entsprechende Rechte. Bewerbungen unter [https://docs.google.com/forms/d/e/1FAIpQLSfjxdTCI7b4Lh0KrQQRdq068PA8mGURXSB49gMEb9ZMFOWwRg/viewform Link] | |- | Country Manager (CM) || Steht landesweit den Usern unterstützend/beratend zur Seite. Ein CM setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um und überwacht auch deren Einhaltung durch die User. Der CM arbeitet aktiv an der Weiterentwicklung der Regeln sowie deren Beschreibung mit. Er ist im Forum aktiv und per PM erreichbar. || Geeignete Kandidaten werden angesprochen |} =Rechte basierend auf Fahrten= Jeder Benutzer erhält Rechte auf den mit Waze befahrenen Straßen. Die Rechte anhand der befahrenen Straßen sind abhängig von der Stufe des Benutzers und gelten für einen vordefinierten Radius, wie in der Tabelle oben angegeben. Die Rechte, die Du während einer Fahrt erlangst, verfallen nach 3 Monaten wieder. Wenn Du ein Gebiet befahren hast, ist es daher ratsam, Änderungen oder Verbesserungen an der Karte sobald wie möglich vorzunehmen. =Rechte im Karteneditor= ==Gesperrte Segmente== Wenn ein Editor ein Segment auf eine Stufe sperrt, schützt er das Segment vor unbedachtem Bearbeiten neuer Benutzer oder Benutzer mit niedrigerer Stufe. ===Fähigkeit ein Segment zu bearbeiten=== Ein Segment kann nicht von einem Benutzer mit niedrigerer Stufe als die am Segment eingestellte Sperr-Stufe bearbeitet werden. Beispiel: Du findest ein Segment, welches auf Stufe 2 gesperrt ist. Du musst die Stufe 2 oder höher UND die Rechte im Gebiet besitzen ("Meine Gebiete" im Karteneditor), um dieses Segment bearbeiten zu können. ===Fähigkeit einen Blitzer zu bearbeiten=== Der letzte Benutzer, der einen Blitzer bearbeitet hat, sperrt diesen automatisch auf seine Stufe. Ein Benutzer mit tieferer Stufe kann den Blitzer nicht ändern oder löschen, sofern er nicht der Besitzer (Melder) ist. ==Area-Manager== [[Der Area Manager|Area-Manager]] können alles bearbeiten in ihren Gebieten, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. Eine Liste von Area-Managern gibt es [[Der_Area_Manager#AM-Liste|hier]]. ==Country-Manager== Country-Manager können alles in dem Land bearbeiten, für das sie Country-Manager sind, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. =Ein Wort der Mahnung= Beim Bearbeiten der Karte erklärst du dich damit einverstanden, die Wiki-Standards einzuhalten, die durch die Community in Deinem Land definiert wurden. Die Einhaltung der dort festgelegten Regeln und Vorschriften ist notwendig, da reale Personen im wirklichen Leben sich auf unsere Arbeit verlassen! Solltest du Fragen haben, wende dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit dir zu helfen. Ausserdem erreichst Du oft höherrangige Editoren (Level 4, 5, 6) über den Editor-Chat. Wir helfen gern und beantworten Neulingen gern immer wieder die typischen Fragen... ;-) !Beachte: Wenn du nicht nach den Richtlinien arbeitest, kannst du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn du nicht erreichbar bist und auf persönliche Nachrichten (PM) - insbesondere von Country Managern deines Landes oder Mails vom Waze-Hauptquartier - nicht antwortest, wirst du herabgestuft und deine Bearbeitungsrechte sowie deine erlangten Stufen werden dir entzogen. Dies kann sogar bis zur Sperre der Editierrechte gehen! Wir dulden keinen Vandalismus, und wir brauchen keine unbekannten Gebietsfürsten! <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] f40c17082ea86d2fa8764d8177bb7bc910e35de2 12071 12070 2019-07-03T19:48:39Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] = Die verschiedenen Stufen = Du kannst Deine eigene [[WME Oberfläche und Steuerelemente#Ich|Stufe]] im Waze Karteneditor oben links unter deinem Benutzernamen einsehen. Die Stufen werden anhand von orangefarbenen Pilonen dargestellt.<br/>Wenn Du eine Straße im Karteneditor auswählst, kannst Du ebenso Deine Stufe einsehen, wenn Du die Straße erstellt, aufgezeichnet oder bearbeitet hast (vorher speichern). Die Stufe steht hinter dem Benutzernamen in Klammern.<br/>Beispiel: Benutzer(0) Wenn Deine Stufe tiefer ist als erwartet - basierend auf den Kriterien, die unten aufgeführt sind (Ersichtlich im [[Mein Dashboard#Your Rank and Points|Dashboard]] unter Map-Updates), melde dies im [[Glossar#DACH|DACH-Raum]] dem Selfmanagement-Team, resp. einem Manager Deines Landes (per [https://www.waze.com/forum/ucp.php?i=pm&mode=compose PM im Forum]). Selfmanagement-Team für alle DACH-Länder: *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *popel22 (CH) *Vince1612 (CH) * {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Level-Tabelle" |- ! Stufe / Pilonen !! Edit-Radius !! Erforderliche Mindest-Edits !! Beschreibung !! Art der Beantragung |- |class="unsortable" align="center" | 1 ||class="unsortable" align="center" | 1,6 km ||class="unsortable" align="center" | 0 || Macht sich mit dem [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] und dem [https://www.waze.com/forum/viewforum.php?f=24 Forum] vertraut. || |- |class="unsortable" align="center" | 2 ||class="unsortable" align="center" | 3,2 km ||class="unsortable" align="center" | 3.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und orientiert sich an den Regeln. Stellt (spätestens jetzt) erste Fragen im [https://www.waze.com/forum/viewforum.php?f=24 Forum], um sich weiter zu verbessern. || Hochstufung erfolgt automatisch |- |class="unsortable" align="center" | 3 ||class="unsortable" align="center" | 4,8 km ||class="unsortable" align="center" | 25.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Ist im [https://www.waze.com/forum/viewforum.php?f=24 Forum] präsent und ist per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 4 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 100.000 || Dieselben Kriterien wie Stufe 3 || PM an Self-Management-Team |- |class="unsortable" align="center" | 5 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 250.000 || Setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um. Ist im Forum aktiv und per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 6 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 500.000 || || PM an Self-Management-Team |} Unabhängig von den Edit-Stufen gibt es die Rollen ''Area Manager (AM)'' sowie ''Country Manager (CM)'': {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Rollen-Tabelle" |- ! Rolle !! Beschreibung !! Art der Beantragung |- | Area Manager (AM) || Steht in seinem AM-Gebiet den Usern unterstützend/beratend zur Seite. Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Lock-Regeln (sprich: er kann nur Segmente bis zu seinem Edit-Level bearbeiten, wie alle). Ein AM hat das Wiki gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Er ist im Forum präsent und per PM erreichbar.|| [[Der_Area_Manager|AM-Formular]] |- |State Manager (SM) |Steht in seinem SM-Gebiet (Kanton) den Usern unterstützend/beratend zur Seite. Sein SM-Gebiet ist immer als ganzes für dem SM zum Bearbeiten freigeschaltet, der SM untersteht aber den normalen Lock-Regeln (sprich: er kann nur Segmente bis zu seinem Edit-Level bearbeiten, wie alle). Ein SM hat das Wiki gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Er ist im Forum präsent und per PM erreichbar. | |- |''RTC State Manager'' |Dies ist eine Spezialrolle, die es bisher nur in der Schweiz gibt. Der ''RTC State Manager'' ist in einem oder mehreren Kantonen für Strassensperrungen zuständig und erhält entsprechende Rechte. |Bewerbungen unter [https://docs.google.com/forms/d/e/1FAIpQLSfjxdTCI7b4Lh0KrQQRdq068PA8mGURXSB49gMEb9ZMFOWwRg/viewform Link] |- | Country Manager (CM) || Steht landesweit den Usern unterstützend/beratend zur Seite. Ein CM setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um und überwacht auch deren Einhaltung durch die User. Der CM arbeitet aktiv an der Weiterentwicklung der Regeln sowie deren Beschreibung mit. Er ist im Forum aktiv und per PM erreichbar. || Geeignete Kandidaten werden angesprochen |} =Rechte basierend auf Fahrten= Jeder Benutzer erhält Rechte auf den mit Waze befahrenen Straßen. Die Rechte anhand der befahrenen Straßen sind abhängig von der Stufe des Benutzers und gelten für einen vordefinierten Radius, wie in der Tabelle oben angegeben. Die Rechte, die Du während einer Fahrt erlangst, verfallen nach 3 Monaten wieder. Wenn Du ein Gebiet befahren hast, ist es daher ratsam, Änderungen oder Verbesserungen an der Karte sobald wie möglich vorzunehmen. =Rechte im Karteneditor= ==Gesperrte Segmente== Wenn ein Editor ein Segment auf eine Stufe sperrt, schützt er das Segment vor unbedachtem Bearbeiten neuer Benutzer oder Benutzer mit niedrigerer Stufe. ===Fähigkeit ein Segment zu bearbeiten=== Ein Segment kann nicht von einem Benutzer mit niedrigerer Stufe als die am Segment eingestellte Sperr-Stufe bearbeitet werden. Beispiel: Du findest ein Segment, welches auf Stufe 2 gesperrt ist. Du musst die Stufe 2 oder höher UND die Rechte im Gebiet besitzen ("Meine Gebiete" im Karteneditor), um dieses Segment bearbeiten zu können. ===Fähigkeit einen Blitzer zu bearbeiten=== Der letzte Benutzer, der einen Blitzer bearbeitet hat, sperrt diesen automatisch auf seine Stufe. Ein Benutzer mit tieferer Stufe kann den Blitzer nicht ändern oder löschen, sofern er nicht der Besitzer (Melder) ist. ==Area-Manager== [[Der Area Manager|Area-Manager]] können alles bearbeiten in ihren Gebieten, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. Eine Liste von Area-Managern gibt es [[Der_Area_Manager#AM-Liste|hier]]. ==Country-Manager== Country-Manager können alles in dem Land bearbeiten, für das sie Country-Manager sind, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. =Ein Wort der Mahnung= Beim Bearbeiten der Karte erklärst du dich damit einverstanden, die Wiki-Standards einzuhalten, die durch die Community in Deinem Land definiert wurden. Die Einhaltung der dort festgelegten Regeln und Vorschriften ist notwendig, da reale Personen im wirklichen Leben sich auf unsere Arbeit verlassen! Solltest du Fragen haben, wende dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit dir zu helfen. Ausserdem erreichst Du oft höherrangige Editoren (Level 4, 5, 6) über den Editor-Chat. Wir helfen gern und beantworten Neulingen gern immer wieder die typischen Fragen... ;-) !Beachte: Wenn du nicht nach den Richtlinien arbeitest, kannst du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn du nicht erreichbar bist und auf persönliche Nachrichten (PM) - insbesondere von Country Managern deines Landes oder Mails vom Waze-Hauptquartier - nicht antwortest, wirst du herabgestuft und deine Bearbeitungsrechte sowie deine erlangten Stufen werden dir entzogen. Dies kann sogar bis zur Sperre der Editierrechte gehen! Wir dulden keinen Vandalismus, und wir brauchen keine unbekannten Gebietsfürsten! <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 09f137adc859900e6603c437a27703082c45f5a3 12072 12071 2019-07-03T19:57:29Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] = Die verschiedenen Stufen = Du kannst Deine eigene [[WME Oberfläche und Steuerelemente#Ich|Stufe]] im Waze Karteneditor oben links unter deinem Benutzernamen einsehen. Die Stufen werden anhand von orangefarbenen Pilonen dargestellt.<br/>Wenn Du eine Straße im Karteneditor auswählst, kannst Du ebenso Deine Stufe einsehen, wenn Du die Straße erstellt, aufgezeichnet oder bearbeitet hast (vorher speichern). Die Stufe steht hinter dem Benutzernamen in Klammern.<br/>Beispiel: Benutzer(0) Wenn Deine Stufe tiefer ist als erwartet - basierend auf den Kriterien, die unten aufgeführt sind (Ersichtlich im [[Mein Dashboard#Your Rank and Points|Dashboard]] unter Map-Updates), melde dies im [[Glossar#DACH|DACH-Raum]] dem Selfmanagement-Team, resp. einem Manager Deines Landes (per [https://www.waze.com/forum/ucp.php?i=pm&mode=compose PM im Forum]). Selfmanagement-Team für alle DACH-Länder: *Snake68 (D) *BellHouse (D) *TSWA (AT) *GPSRitter (AT) *popel22 (CH) *Vince1612 (CH) * {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Level-Tabelle" |- ! Stufe / Pilonen !! Edit-Radius !! Erforderliche Mindest-Edits !! Beschreibung !! Art der Beantragung |- |class="unsortable" align="center" | 1 ||class="unsortable" align="center" | 1,6 km ||class="unsortable" align="center" | 0 || Macht sich mit dem [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] und dem [https://www.waze.com/forum/viewforum.php?f=24 Forum] vertraut. || |- |class="unsortable" align="center" | 2 ||class="unsortable" align="center" | 3,2 km ||class="unsortable" align="center" | 3.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und orientiert sich an den Regeln. Stellt (spätestens jetzt) erste Fragen im [https://www.waze.com/forum/viewforum.php?f=24 Forum], um sich weiter zu verbessern. || Hochstufung erfolgt automatisch |- |class="unsortable" align="center" | 3 ||class="unsortable" align="center" | 4,8 km ||class="unsortable" align="center" | 25.000 || Hat das [[Anleitung_zum_Bearbeiten_der_Karte|Wiki]] gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Ist im [https://www.waze.com/forum/viewforum.php?f=24 Forum] präsent und ist per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 4 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 100.000 || Dieselben Kriterien wie Stufe 3 || PM an Self-Management-Team |- |class="unsortable" align="center" | 5 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 250.000 || Setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um. Ist im Forum aktiv und per PM erreichbar. || PM an Self-Management-Team |- |class="unsortable" align="center" | 6 ||class="unsortable" align="center" | 6,4 km ||class="unsortable" align="center" | 500.000 || || PM an Self-Management-Team |} Unabhängig von den Edit-Stufen gibt es die Rollen ''Area Manager (AM)'' sowie ''Country Manager (CM)'': {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" id="Rollen-Tabelle" |- ! Rolle !! Beschreibung !! Art der Beantragung |- | Area Manager (AM) || Steht in seinem AM-Gebiet den Usern unterstützend/beratend zur Seite. Sein AM-Gebiet ist immer als ganzes für dem AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Lock-Regeln (sprich: er kann nur Segmente bis zu seinem Edit-Level bearbeiten, wie alle). Ein AM hat das Wiki gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Er ist im Forum präsent und per PM erreichbar.|| [[Der_Area_Manager|AM-Formular]] |- |State Manager (SM) |Steht in seinem SM-Gebiet (Kanton) den Usern unterstützend/beratend zur Seite. Sein SM-Gebiet ist immer als ganzes für dem SM zum Bearbeiten freigeschaltet, der SM untersteht aber den normalen Lock-Regeln (sprich: er kann nur Segmente bis zu seinem Edit-Level bearbeiten, wie alle). Ein SM hat das Wiki gelesen und setzt die dort aufgeführten Regeln bei seinen Edits konsequent um. Er ist im Forum präsent und per PM erreichbar. |PM an einen CM |- |''RTC State Manager'' |Dies ist eine Spezialrolle, die es bisher nur in der Schweiz gibt. Der ''RTC State Manager'' ist in einem oder mehreren Kantonen für Strassensperrungen zuständig und erhält entsprechende Rechte. |Bewerbungen unter [https://docs.google.com/forms/d/e/1FAIpQLSfjxdTCI7b4Lh0KrQQRdq068PA8mGURXSB49gMEb9ZMFOWwRg/viewform Link] |- | Country Manager (CM) || Steht landesweit den Usern unterstützend/beratend zur Seite. Ein CM setzt die Regeln des Wiki bei jedem Edit vorbildlich und konsequent um und überwacht auch deren Einhaltung durch die User. Der CM arbeitet aktiv an der Weiterentwicklung der Regeln sowie deren Beschreibung mit. Er ist im Forum aktiv und per PM erreichbar. || Geeignete Kandidaten werden angesprochen |} =Rechte basierend auf Fahrten= Jeder Benutzer erhält Rechte auf den mit Waze befahrenen Straßen. Die Rechte anhand der befahrenen Straßen sind abhängig von der Stufe des Benutzers und gelten für einen vordefinierten Radius, wie in der Tabelle oben angegeben. Die Rechte, die Du während einer Fahrt erlangst, verfallen nach 3 Monaten wieder. Wenn Du ein Gebiet befahren hast, ist es daher ratsam, Änderungen oder Verbesserungen an der Karte sobald wie möglich vorzunehmen. =Rechte im Karteneditor= ==Gesperrte Segmente== Wenn ein Editor ein Segment auf eine Stufe sperrt, schützt er das Segment vor unbedachtem Bearbeiten neuer Benutzer oder Benutzer mit niedrigerer Stufe. ===Fähigkeit ein Segment zu bearbeiten=== Ein Segment kann nicht von einem Benutzer mit niedrigerer Stufe als die am Segment eingestellte Sperr-Stufe bearbeitet werden. Beispiel: Du findest ein Segment, welches auf Stufe 2 gesperrt ist. Du musst die Stufe 2 oder höher UND die Rechte im Gebiet besitzen ("Meine Gebiete" im Karteneditor), um dieses Segment bearbeiten zu können. ===Fähigkeit einen Blitzer zu bearbeiten=== Blitzer wurden in der Schweiz deaktiviert. Ab und zu taucht trotzdem noch einer auf. In so einem Fall bitte PM an einen CM. ==Area-Manager== [[Der Area Manager|Area-Manager]] können alles bearbeiten in ihren Gebieten, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. ==Country-Manager== Country-Manager können alles in dem Land bearbeiten, für das sie Country-Manager sind, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. Liste der CMs [http://www.waze-switzerland.ch/contact hier] == Editor State Manager (SM) == Editor State Manager können alles in dem Kanton bearbeiten, für den sie SM sind, außer, wenn etwas durch einen Benutzer mit höherer Stufe gesperrt wurde. Liste der SMs [http://www.waze-switzerland.ch/contact hier] =Ein Wort der Mahnung= Beim Bearbeiten der Karte erklärst du dich damit einverstanden, die Wiki-Standards einzuhalten, die durch die Community in Deinem Land definiert wurden. Die Einhaltung der dort festgelegten Regeln und Vorschriften ist notwendig, da reale Personen im wirklichen Leben sich auf unsere Arbeit verlassen! Solltest du Fragen haben, wende dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit dir zu helfen. Ausserdem erreichst Du oft höherrangige Editoren (Level 4, 5, 6) über den Editor-Chat. Wir helfen gern und beantworten Neulingen gern immer wieder die typischen Fragen... ;-) !Beachte: Wenn du nicht nach den Richtlinien arbeitest, kannst du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn du nicht erreichbar bist und auf persönliche Nachrichten (PM) - insbesondere von Country Managern deines Landes oder Mails vom Waze-Hauptquartier - nicht antwortest, wirst du herabgestuft und deine Bearbeitungsrechte sowie deine erlangten Stufen werden dir entzogen. Dies kann sogar bis zur Sperre der Editierrechte gehen! Wir dulden keinen Vandalismus, und wir brauchen keine unbekannten Gebietsfürsten! <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 23be0f30b220a8b0ad3d9522acd036794c0cd77c 6 106 12074 2019-07-09T10:12:30Z Popel22 24 wikitext text/x-wiki Fusswege mit "Ghost-Nodes" d53eda07ba7ede78d1149171987579f27415bc22 0 14 12075 10830 2019-07-09T10:32:17Z Popel22 24 /* Fußwege */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Vielleicht bist Du auch einmal auf einen Fußweg geleitet worden oder in eine Straße, in der Du nicht fahren darfst und fragst Dich, wie sich das vermeiden lässt? Hier findest Du die Antwort auf solche Fragen. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. ===== Fusswege '''dürfen''' ans Strassennetz angeschlossen werden. ===== [[Datei:Fusswege mit "Ghost-Nodes".jpg|links|miniatur|403x403px]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone (PB = Fussgängerzone / WT = Fussweg) [[Datei:WTvsPB.png|links|miniatur|518x518px]] === '''ACHTUNG - UNTEN STEHENDER ARTIKEL ÜBER FUSSWEGE IST VERALTET, ÜBERARBEITUNG SOON''' === =Fußwege= <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ==Beispiele== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] ==Ein Tipp== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 0c93f6fc5c14096de09243b89be9f79daa948d41 0 14 12076 12075 2019-07-10T08:16:55Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. ===== Fusswege '''dürfen''' ans Strassennetz angeschlossen werden. ===== [[Datei:Fusswege mit "Ghost-Nodes".jpg|links|miniatur|403x403px]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone (PB = Fussgängerzone / WT = Fussweg) [[Datei:WTvsPB.png|links|miniatur|518x518px]] == '''ACHTUNG - UNTEN STEHENDER ARTIKEL ÜBER FUSSWEGE IST VERALTET, ÜBERARBEITUNG SOON''' == =Fußwege= <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ==Beispiele== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] ==Ein Tipp== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] d2e8540f512ff71282d8dc0f28ca39eae36cb1dd 12077 12076 2019-07-10T08:20:01Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. '''Fusswege dürfen ans Strassennetz angeschlossen werden.'''[[Datei:Fusswege mit "Ghost-Nodes".jpg|links|miniatur|403x403px]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone (PB = Fussgängerzone / WT = Fussweg) [[Datei:WTvsPB.png|links|miniatur|518x518px]] ='''ACHTUNG - UNTEN STEHENDER ARTIKEL ÜBER FUSSWEGE IST VERALTET, ÜBERARBEITUNG SOON'''= <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ==Beispiele== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] ==Ein Tipp== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] c03c193383123dc76ab2b25b0484a8c53318e393 12078 12077 2019-07-10T08:25:48Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. '''Fusswege dürfen ans Strassennetz angeschlossen werden.'''[[Datei:Fusswege mit "Ghost-Nodes".jpg|links|miniatur|403x403px]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone[[Datei:WTvsPB.png|links|miniatur|518x518px]] (PB = Fussgängerzone / WT = Fussweg) == '''ACHTUNG - UNTEN STEHENDER ARTIKEL ÜBER FUSSWEGE IST VERALTET, ÜBERARBEITUNG SOON''' == <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ==Beispiele== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] ==Ein Tipp== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 4769f6422ec9fda1c1a5d312fa970f416c92d860 12079 12078 2019-07-10T08:30:06Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. '''Fusswege dürfen ans Strassennetz angeschlossen werden.'''[[Datei:Fusswege mit "Ghost-Nodes".jpg|miniatur|403x403px|ohne]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone[[Datei:WTvsPB.png|miniatur|518x518px|ohne]] (PB = Fussgängerzone / WT = Fussweg) == '''ACHTUNG - UNTEN STEHENDER ARTIKEL ÜBER FUSSWEGE IST VERALTET, ÜBERARBEITUNG SOON''' == <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ==Beispiele== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] ==Ein Tipp== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] bc8c5811abffe6da1b7b6da46c26fec569450190 12080 12079 2019-07-10T08:31:53Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. '''Fusswege dürfen ans Strassennetz angeschlossen werden.'''[[Datei:Fusswege mit "Ghost-Nodes".jpg|miniatur|403x403px|ohne]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone[[Datei:WTvsPB.png|miniatur|518x518px|ohne]] (PB = Fussgängerzone / WT = Fussweg) == ACHTUNG - UNTEN STEHENDER ARTIKEL ÜBER '''FUSSWEGE''' IST VERALTET, ÜBERARBEITUNG SOON == <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ==Beispiele== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] ==Ein Tipp== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 6867b8488f6e34c1fed4c01e2c43de9a1be58e7b 12081 12080 2019-07-10T08:33:36Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. '''Fusswege dürfen ans Strassennetz angeschlossen werden.'''[[Datei:Fusswege mit "Ghost-Nodes".jpg|miniatur|403x403px|ohne]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone[[Datei:WTvsPB.png|miniatur|518x518px|ohne]] (PB = Fussgängerzone / WT = Fussweg) == ACHTUNG - UNTEN STEHENDER ARTIKEL ÜBER '''FUSSWEGE''' IST VERALTET, ÜBERARBEITUNG SOON == <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ===Beispiele=== Am Ende einer Straße befindet sich ein Fußweg. Dieses Bild zeigt, wie es '''nicht''' aussehen soll. [[File:Fussweg-falsch.png|center|frame|Falsch!]] <br> Dieses Bild zeigt, wie es aussehen soll. Der Fußweg am Ende wird nicht benötigt, sofern er keinen anderen Namen hat, als das Straßensegment. Die zusätzliche Kreuzung wird entfernt. Mögliche Fehler (Routings) und Fehlerquellen, wie falsche Abbiegungen der zusätzlichen Kreuzung auf der "Talstraße" können so ausgeschlossen werden. [[File:Fussweg-richtig.png|center|frame|Richtig!]] <br> Hat der Fußweg einen anderen Namen, als das Straßen-Segment, wird es dementsprechend benannt und abgetrennt von der "Talstraße". Die verbliebene Kreuzung wird gelöscht. [[File:Fussweg-name.png|center|frame|Fußweg besitzt anderen Namen.]] <br> [[File:Abgetrennt1.png|center|frame|Alle Fußwege sind hier isoliert vom Straßennetz. Ersparnis: 4 unnötige Kreuzungen.]] <br> [[File:Abgetrennt2.png|center|frame|Auch hier sind alle Fußwege abgetrennt vom Straßennetz. Ersparnis: 5 unnötige Kreuzungen.]] <br> [[File:Abgetrennt3.png|center|frame|Ein weiteres prominentes Beispiel, das bei einer Straßensperrung ein fehlerhaftes Routing provozieren könnte, wenn es mit den Straßen verbunden wäre.]] <br> [[File:Abgetrennt4.png|center|frame|Hier ein Beispiel, bei dem die Namen ändern auf den Straßen-Segmenten. Da die Kreuzung sowieso die Namen trennen muss, kann der Fußweg als Sackgasse verbleiben. Falls so ein Beispiel Probleme verursacht, dann trenne den Fußweg ab.]] <br> [[File:Abgetrennt5.png|center|frame|Noch ein Beispiel mit Namensänderung und Fußweg als Sackgasse.]] ===Ein Tipp=== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. Wenn Du an der rohen [[Häufig_gestellte_Fragen#Was_ist_die_Base-Map.3F|Base-Map]] arbeitest, denke an diesen Tipp. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 6aa64464daebbdc5cbf15dbbeaaf2385fa8e4ac2 0 78 12082 12068 2019-07-13T12:32:14Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. b56daffd733317745de1b3e9d3d921f5f13303c0 12085 12082 2019-08-12T09:42:34Z Vince1612 23 Ajout d'un point wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Utilisation du type "Rue étroite" (Narrow Street) == Texte. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 4285d363fb244a4586d64399a8ba5578d072d4fa 12086 12085 2019-08-12T09:43:36Z Vince1612 23 /* Utilisation du type "Rue étroite" (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type ''Rue étroite'' (''Narrow Street'') == Texte. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 52ae978f2052f400c1be58c5650c26e5c256392a 12087 12086 2019-08-12T09:45:17Z Vince1612 23 /* Type Rue étroite (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite (Narrow Street) == Texte. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 71b6baf9bbe80b2ffa372c24462306824a40a41f 12088 12087 2019-08-12T09:46:43Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite (Narrow Street) == Texte. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 33df411bbfd81c5e6f44ff9fca0744e2dc452cf7 12089 12088 2019-08-12T09:48:19Z Vince1612 23 /* Type: Rue étroite (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Texte. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. e6f20ec93bdbe8030bf1feb70c2383af362f8bd5 12090 12089 2019-08-12T09:49:32Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Texte. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 30b372a665355ad8b3cae9d45274eb6e7ea09415 12091 12090 2019-08-12T09:50:19Z Vince1612 23 /* Culs-de-sac */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Texte. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 6c5b777fa405a0ae4b4b1c92ddb13a5ba49bf581 12092 12091 2019-08-12T10:18:29Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communauté pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse cependant nous avons établi quelques règles à suivre: * Quand peut-on utiliser ce type en Suisse? - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * Quand ne doit-on pas utiliser ce type? - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment est étroit mais permet le croisement de véhicules standards, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. b4f085442164e5e37af05f817da18d783ce9972a 12093 12092 2019-08-12T10:23:28Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse cependant nous avons établi quelques règles à suivre: * Quand peut-on utiliser ce type en Suisse? - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * Quand ne doit-on pas utiliser ce type? - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment est étroit mais permet le croisement de véhicules standards, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. f88c806452e95bdff4c421eb9534ad5a88cead56 12094 12093 2019-08-12T10:26:26Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse cependant nous avons établi quelques règles à suivre: * Quand peut-on utiliser ce type en Suisse? - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * Quand ne doit-on pas utiliser ce type? - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment est étroit mais permet le croisement de véhicules standards, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * Autres cas: Voir le sujet du forum sur les ''routes à travers champs:'' https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 5a0610c062e8ae1276f5ef34c7547e2b612273e5 12095 12094 2019-08-12T10:27:49Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment est étroit mais permet le croisement de véhicules standards, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 03f08e7d782106441a9d2a0a4df8c919af306ebf 12096 12095 2019-08-12T10:41:39Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 0ddc4c59f60f8945267e054cbba9b051c8b24926 12097 12096 2019-08-12T11:00:43Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) === Chaque boucle doit être formée d'au moins trois (3) segments! === Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 58bc7ffe0e2232ac027f895a913305665060c196 12098 12097 2019-08-12T11:07:01Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ==== Chaque boucle doit être formée d'au moins trois (3) segments! ==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 00a70f97b2cd53c6549a983d5ec7fb75181eb95c 12099 12098 2019-08-12T12:08:29Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ==== Chaque boucle doit être formée d'au moins trois (3) segments! ==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 43ff406dddfa6721a59c82e877b6e1266ab90e93 12100 12099 2019-08-12T12:58:19Z Vince1612 23 wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ==== Chaque boucle doit être formée d'au moins trois (3) segments! ==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. c0310f7e52c667455272f38f5e6d3a1a5544e6bb 12101 12100 2019-08-12T13:02:21Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ==== Chaque boucle doit être formée d'au moins trois (3) segments! ==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment est déjà ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. b5251d98638a37299898b67b42379dc1f780bd0c 12102 12101 2019-08-12T13:04:51Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ==== Chaque boucle doit être formée d'au moins trois (3) segments! ==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment est ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. c6bbc189169ab4f56082e4f89c96472624b707b5 12103 12102 2019-08-24T09:10:46Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' == Nommage des segments == Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : * "Chemin" et non "Ch." * "Route" et non "Rte" * "Rue de la Paix" et non "rue de la paix" * Etc... == Parkings et aires de stationnement == === Voies de parking === Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: * Les entrées/sorties connectées aux routes du réseau routier * Les voies qui longent le(s) commerce(s) ou bâtiment(s) * Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) * Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. === Lieux (POIs) et zones de parking === L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' * '''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" * '''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. == Les voies privées (habitations) == Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: * La voie sert à accéder à <u>au moins</u> deux habitations. * La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) * Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) == Demi tours (U-turns) == Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: # Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac # Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #* Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #* Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation == Segments trop courts (micro-segments) == La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. == Boucles (Loops) == Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ==== Chaque boucle doit être formée d'au moins trois (3) segments! ==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ==== Boucle à deux segments (erreur la plus courante) ==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ==== Boucle à un segment ==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. ===== Boucles à un segment formant un détour ===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. ===== Boucles à un segment formant un demi-tour dans un cul-de-sac ===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. == Culs-de-sac == Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. == Type: Rue étroite, Ruelle (Narrow Street) == Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: * '''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *# le segment est à double sens, et que *# le segment fait plus de 50m, et que *# le segment n'est assez large que pour un seul véhicule standard à la fois. * '''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *# le segment est à sens unique, ou que *# le segment est un court passage sous voies ou un petit pont, ou que *# le segment est un cul-de-sac rattaché directement à un autre type de route (Rue, etc...), ou que *# le segment est ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *# le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *# le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *# le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *# le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place, et finalement *# la cartographie de villages entiers avec ce type est interdite, ou doit impérativement faire l'objet d'une discussion sur le forum au préalable. * '''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' == Notes == Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. f67f09f2ba2c4f40ebb498c320b30ddccc357b6f 12108 12103 2020-05-18T22:35:48Z Vince1612 23 /* Type: Rue étroite, Ruelle (Narrow Street) */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' ==Nommage des segments== Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : *"Chemin" et non "Ch." *"Route" et non "Rte" *"Rue de la Paix" et non "rue de la paix" *Etc... ==Parkings et aires de stationnement== ===Voies de parking=== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: *Les entrées/sorties connectées aux routes du réseau routier *Les voies qui longent le(s) commerce(s) ou bâtiment(s) *Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) *Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ===Lieux (POIs) et zones de parking=== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' *'''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" *'''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. ==Les voies privées (habitations)== Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: *La voie sert à accéder à <u>au moins</u> deux habitations. *La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) *Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) ==Demi tours (U-turns)== Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: #Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac #Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #*Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #*Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation ==Segments trop courts (micro-segments)== La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. ==Boucles (Loops)== Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ====Chaque boucle doit être formée d'au moins trois (3) segments!==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ====Boucle à deux segments (erreur la plus courante)==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ====Boucle à un segment==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. =====Boucles à un segment formant un détour===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. =====Boucles à un segment formant un demi-tour dans un cul-de-sac===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. ==Culs-de-sac== Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. ==Type: Rue étroite, Ruelle (Narrow Street)== Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: *'''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *#le segment est à double sens, et que *#le segment fait plus de 50m, et que *#le segment n'est assez large que pour un seul véhicule standard à la fois. *'''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *#le segment est à sens unique, ou que *#le segment est un court passage sous voies ou un petit pont, ou que *#le segment est un cul-de-sac ou sert d'accès à une vallée en cul-de-sac ne pouvant pas servir de transit, ou que *#le segment est ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *#le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *#le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *#le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *#le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place, et finalement *#la cartographie de villages entiers avec ce type est interdite, ou doit impérativement faire l'objet d'une discussion sur le forum au préalable. *'''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' ==Notes== Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 1b2b005ed66a8d10c73607452d762de787aca28d 12109 12108 2020-08-17T17:43:28Z Vince1612 23 Ajout chemins piétons wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' ==Nommage des segments== Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : *"Chemin" et non "Ch." *"Route" et non "Rte" *"Rue de la Paix" et non "rue de la paix" *Etc... ==Parkings et aires de stationnement== ===Voies de parking=== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: *Les entrées/sorties connectées aux routes du réseau routier *Les voies qui longent le(s) commerce(s) ou bâtiment(s) *Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) *Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ===Lieux (POIs) et zones de parking=== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' *'''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" *'''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. ==Les chemin piétons== Il en existe deux type: #Chemin piéton (routable) / Walking Trail #Chemin piéton non-routable / Pedestrian Boardwalk Waze est '''avant tout''' une application destinée aux automobiles, taxi et au deux-roues motorisés. En aucun cas un GPS pour piétons ou vélos. Il convient donc de n'ajouter des chemins pédestres que lorsqu'ils peuvent soit: * Apporter une aide visuelle à un conducteur pour se repérer (notamment lorsque le segment piéton a un nom connu) * Permettre à un conducteur d'être guidé jusqu'à un accès correcte à sa destination, si celle-ci n'est pas accessible autrement qu'à pieds, à l'aide du type 1. Merci d'avance donc de ne pas cartographier les segments n'apportant aucune aide et surchargeant l'affichage intuilement, tel que les trottoirs le longs des routes ou des chemins non-visibles depuis les routes, qui ne permettront pas à un conducteur de mieux s'orienter. * ==Les voies privées (habitations)== Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: *La voie sert à accéder à <u>au moins</u> deux habitations. *La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) *Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) ==Demi tours (U-turns)== Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: #Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac #Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #*Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #*Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation ==Segments trop courts (micro-segments)== La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. ==Boucles (Loops)== Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ====Chaque boucle doit être formée d'au moins trois (3) segments!==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ====Boucle à deux segments (erreur la plus courante)==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ====Boucle à un segment==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. =====Boucles à un segment formant un détour===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. =====Boucles à un segment formant un demi-tour dans un cul-de-sac===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. ==Culs-de-sac== Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. ==Type: Rue étroite, Ruelle (Narrow Street)== Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: *'''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *#le segment est à double sens, et que *#le segment fait plus de 50m, et que *#le segment n'est assez large que pour un seul véhicule standard à la fois. *'''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *#le segment est à sens unique, ou que *#le segment est un court passage sous voies ou un petit pont, ou que *#le segment est un cul-de-sac ou sert d'accès à une vallée en cul-de-sac ne pouvant pas servir de transit, ou que *#le segment est ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *#le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *#le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *#le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *#le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place, et finalement *#la cartographie de villages entiers avec ce type est interdite, ou doit impérativement faire l'objet d'une discussion sur le forum au préalable. *'''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' ==Notes== Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 0b81c3804b8d4e0ef2254b2b0216bf42ec79c0c3 12110 12109 2020-08-17T18:00:46Z Vince1612 23 /* Les chemin piétons */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' ==Nommage des segments== Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : *"Chemin" et non "Ch." *"Route" et non "Rte" *"Rue de la Paix" et non "rue de la paix" *Etc... ==Parkings et aires de stationnement== ===Voies de parking=== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: *Les entrées/sorties connectées aux routes du réseau routier *Les voies qui longent le(s) commerce(s) ou bâtiment(s) *Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) *Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ===Lieux (POIs) et zones de parking=== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' *'''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" *'''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe (ex. "Parking du Mont-Blanc") utiliser le symbol 🅿️ ou laisser le champ vide. ==Les chemins piétons== Il en existe deux type: #Chemin piéton (routable) / Walking Trail #Chemin piéton non-routable / Pedestrian Boardwalk Waze est '''avant tout''' une application destinée aux automobiles, taxi et au deux-roues motorisés. En aucun cas un GPS pour piétons ou vélos. Il convient donc de n'ajouter des chemins pédestres que lorsqu'ils peuvent soit: *Apporter une aide visuelle à un conducteur pour se repérer (notamment lorsque le segment piéton a un nom connu) *Permettre à un conducteur d'être guidé jusqu'à un accès correcte à sa destination, si celle-ci n'est pas accessible autrement qu'à pieds, à l'aide du type 1. Merci d'avance donc de ne pas cartographier les segments n'apportant aucune aide et surchargeant l'affichage intuilement, tel que les trottoirs le longs des routes ou des chemins non-visibles depuis les routes, qui ne permettront pas à un conducteur de mieux s'orienter. * ==Les voies privées (habitations)== Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: *La voie sert à accéder à <u>au moins</u> deux habitations. *La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) *Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) ==Demi tours (U-turns)== Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: #Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac #Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #*Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #*Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation ==Segments trop courts (micro-segments)== La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. ==Boucles (Loops)== Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ====Chaque boucle doit être formée d'au moins trois (3) segments!==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ====Boucle à deux segments (erreur la plus courante)==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ====Boucle à un segment==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. =====Boucles à un segment formant un détour===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. =====Boucles à un segment formant un demi-tour dans un cul-de-sac===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. ==Culs-de-sac== Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. ==Type: Rue étroite, Ruelle (Narrow Street)== Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: *'''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *#le segment est à double sens, et que *#le segment fait plus de 50m, et que *#le segment n'est assez large que pour un seul véhicule standard à la fois. *'''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *#le segment est à sens unique, ou que *#le segment est un court passage sous voies ou un petit pont, ou que *#le segment est un cul-de-sac ou sert d'accès à une vallée en cul-de-sac ne pouvant pas servir de transit, ou que *#le segment est ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *#le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *#le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *#le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *#le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place, et finalement *#la cartographie de villages entiers avec ce type est interdite, ou doit impérativement faire l'objet d'une discussion sur le forum au préalable. *'''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' ==Notes== Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 8aebc951003408624150f314654727ec3a472cc1 12111 12110 2020-08-18T08:23:02Z Vince1612 23 /* Lieux (POIs) et zones de parking */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' ==Nommage des segments== Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : *"Chemin" et non "Ch." *"Route" et non "Rte" *"Rue de la Paix" et non "rue de la paix" *Etc... ==Parkings et aires de stationnement== ===Voies de parking=== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: *Les entrées/sorties connectées aux routes du réseau routier *Les voies qui longent le(s) commerce(s) ou bâtiment(s) *Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) *Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ===Lieux (POIs) et zones de parking=== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' *'''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" *'''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe et utiliser le symbole 🅿️ (ex. "🅿️ Mont-Blanc") ou laisser le champ vide. ==Les chemins piétons== Il en existe deux type: #Chemin piéton (routable) / Walking Trail #Chemin piéton non-routable / Pedestrian Boardwalk Waze est '''avant tout''' une application destinée aux automobiles, taxi et au deux-roues motorisés. En aucun cas un GPS pour piétons ou vélos. Il convient donc de n'ajouter des chemins pédestres que lorsqu'ils peuvent soit: *Apporter une aide visuelle à un conducteur pour se repérer (notamment lorsque le segment piéton a un nom connu) *Permettre à un conducteur d'être guidé jusqu'à un accès correcte à sa destination, si celle-ci n'est pas accessible autrement qu'à pieds, à l'aide du type 1. Merci d'avance donc de ne pas cartographier les segments n'apportant aucune aide et surchargeant l'affichage intuilement, tel que les trottoirs le longs des routes ou des chemins non-visibles depuis les routes, qui ne permettront pas à un conducteur de mieux s'orienter. * ==Les voies privées (habitations)== Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: *La voie sert à accéder à <u>au moins</u> deux habitations. *La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) *Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) ==Demi tours (U-turns)== Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: #Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac #Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #*Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #*Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation ==Segments trop courts (micro-segments)== La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. ==Boucles (Loops)== Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ====Chaque boucle doit être formée d'au moins trois (3) segments!==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ====Boucle à deux segments (erreur la plus courante)==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ====Boucle à un segment==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. =====Boucles à un segment formant un détour===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. =====Boucles à un segment formant un demi-tour dans un cul-de-sac===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. ==Culs-de-sac== Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. ==Type: Rue étroite, Ruelle (Narrow Street)== Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: *'''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *#le segment est à double sens, et que *#le segment fait plus de 50m, et que *#le segment n'est assez large que pour un seul véhicule standard à la fois. *'''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *#le segment est à sens unique, ou que *#le segment est un court passage sous voies ou un petit pont, ou que *#le segment est un cul-de-sac ou sert d'accès à une vallée en cul-de-sac ne pouvant pas servir de transit, ou que *#le segment est ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *#le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *#le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *#le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *#le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place, et finalement *#la cartographie de villages entiers avec ce type est interdite, ou doit impérativement faire l'objet d'une discussion sur le forum au préalable. *'''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' ==Notes== Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. 7de42f88d1055529511dd4a52427d546018d698e 12112 12111 2020-09-14T09:47:12Z Vince1612 23 /* Les chemins piétons */ wikitext text/x-wiki '''Ces règles pour la Suisse romande se trouvaient précédemment dans des sujets du forum épinglés qui ont été archivés depuis pour laisser place à cette page. Il s'agit donc d'un condensé de ces diverses règles, établi car ce sont souvent ces erreurs que l'on retrouve le plus dans l'éditeur.''' ==Nommage des segments== Lors du nommage des noms de rues, il ne faut pas faire d'abréviations. De plus il y a lieu de respecter la casse des noms propres. Par exemple : *"Chemin" et non "Ch." *"Route" et non "Rte" *"Rue de la Paix" et non "rue de la paix" *Etc... ==Parkings et aires de stationnement== ===Voies de parking=== Lorsque l'on<nowiki> </nowiki>cartographie, le but est l'utilisabilité et la simplicité de la carte. Pour les parkings on essaie donc de ne cartographier que le nécessaire: *Les entrées/sorties connectées aux routes du réseau routier *Les voies qui longent le(s) commerce(s) ou bâtiment(s) *Les voies formant le périmètre du parking (pour empêcher les voitures d'être collées sur une rue proche, ce qui risquerait de déclencher des détections de bouchons pour rien) *Les voies principales qui servent à passer d'une zone du parking à une autre, pour les grands parkings. En<nowiki> </nowiki>particulier on évite de cartographier chaque voie secondaire voir chaque place individuelle (oui, certain l'ont fait...) <br>Représenter<nowiki> </nowiki>tous les segments d'un parking n'apporte aucune plus value pour la navigation. Cela encombre l'affichage sur les smartphones, surcharge l'application et les serveurs de calcul de parcours pour rien. Si vous êtes au milieu d'un parking, Waze vous dira simplement de rejoindre le segment de parking le plus proche en surbrillance et vous serez guidé sans problème jusqu'à la sortie. ===Lieux (POIs) et zones de parking=== L'utilisation de ce repère est réservé aux parkings possédant leur(s) propre(s) voie(s) d'accès et/ou de circulation. Merci de ne pas créer de repère pour les places de stationnement sur le bord ou le long des routes.<br><br>'''Autres détails''' *'''À éviter''' : Utiliser la catégorie "Park" si vous utilisez WME en anglais, celle-ci est réservée aux espaces verts et parcs publics<br>'''Correct''' : Utiliser la catégorie "Parking Lot" *'''À éviter''' : Nommer le parking comme "Parc", "Parking", "P." ou "[P]"<br>'''Correct''' : Nommer avec le nom exacte s'il existe et utiliser le symbole 🅿️ (ex. "🅿️ Mont-Blanc") ou laisser le champ vide. ==Les chemins piétons== Il en existe deux type: #Chemin piéton (routable) / Walking Trail #Chemin piéton non-routable / Pedestrian Boardwalk Waze est '''avant tout''' une application destinée aux automobiles, taxi et au deux-roues motorisés. En aucun cas un GPS pour piétons ou vélos. Il convient donc de n'ajouter des chemins pédestres que lorsqu'ils peuvent soit: *Apporter une aide visuelle à un conducteur pour se repérer (notamment lorsque le segment piéton a un nom connu) *Permettre à un conducteur d'être guidé jusqu'à un accès correcte à sa destination, si celle-ci n'est pas accessible autrement qu'à pieds, à l'aide du type 1. Merci d'avance donc de ne pas cartographier les segments n'apportant aucune aide et surchargeant l'affichage intuilement, tel que les trottoirs le longs des routes ou des chemins cachés et non-visibles depuis les routes (visibles uniquement du ciel, intérieurs de parcs publics ou propriétés privées), qui ne permettront pas à un conducteur de mieux s'orienter. * ==Les voies privées (habitations)== Cartographier<nowiki> </nowiki>chaque allée menant à une villa à proximité directe d'une rue/route alourdi inutilement l'affichage. Le but de Waze n'est pas de vous guider jusqu'à la porte d'entrée des habitations, mais de vous guider à proximiter de l'habitation. Avec les numéros de rues, Waze saura vous guider devant la<nowiki> </nowiki>bonne maison. Merci donc de ne pas cartographier les voies privées d'accès aux résidences sauf si: *La voie sert à accéder à <u>au moins</u> deux habitations. *La voie est particulièrement longue ou l'habitation très éloignée de la route (>100m) *Ne pas cartographier la voie pourrait causer des problèmes de guidage (déterminer ceci nécessite une bonne expérience dans l'édition de carte et le routing) ==Demi tours (U-turns)== Les flèches de demi-tour ne doivent jamais être mises en vert sauf pour les cas suivants: #Un segment à double sens (A<->B) a comme seule connection un sens unique opposé créant un cul-de-sac #Mis à part pour le point 1, le demi-tour rempli <u>toutes</u> ces conditions #*Réalisable sans aucune manoeuvre spéciale (ex: marche arrière) #*Être légal et spécifiquement indiqué par un marquage/peinture au sol, un panneau routier officiel ou un feu de signalisation ==Segments trop courts (micro-segments)== La<nowiki> </nowiki>longueur d'un segment sur Waze doit être de 5m au minimum pour un fonctionnement optimal de la navigation et la mesure de vitesse que Waze<nowiki> </nowiki>enregistre sur chaque segment. Un segment plus court empêche Waze de<nowiki> </nowiki>calculer efficacement le meilleur itinéraire car il ne disposera pas de<nowiki> </nowiki>données complètes pour ses calculs. Attention donc a ne pas créer de micro-segments (<5m) en connectant des segments proche d'autre noeuds de jonction. Vous pouvez éloigner les deux noeuds pour que le segment mesure au minimum 5m ou tenter de connecter tous les segments sur un seul et même noeud à la place. La longueur d'un segment se voit en cliquant dessus pour le sélectionner puis dans le menu à gauche. ==Boucles (Loops)== Des segments forment une boucle lorsque l'on peut partir d'un nœud et revenir sur ce nœud sans devoir passer deux fois sur le même segment ou sans devoir faire demi-tour pour revenir en arrière. (/!\ ≠ ronds-points) ====Chaque boucle doit être formée d'au moins trois (3) segments!==== Toute boucle ne respectant pas cette règle peut causer des problèmes de guidage plus ou moins sérieux suivant les cas. S'il n'y a aucune rue existante qu'il serait possible de connecter à la boucle pour la diviser en plusieurs segments, il est quand même nécessaire d'ajouter suffisamment de nœuds de jonction à celle-ci pour la diviser en au moins trois segments. Beaucoup de jeunes éditeurs voient ces nœuds additionnels comme étant superflus ou inutiles et les suppriment, ceci peut briser le guidage sur des boucles qui fonctionnaient bien jusqu'ici. Merci d'y prêter attention et d'éduquer les nouveaux éditeurs que vous voyez faire cela. ====Boucle à deux segments (erreur la plus courante)==== Les boucles à deux segments créent une situation appelée "same endpoint drivable segments" ''(FR: segments avec nœuds de fin identiques")'' ou "same connection segments" ''(FR: segment avec la même connexion)''. Cela est un problème car sur l'application, le serveur de navigation ne considère que de quel nœud à quel autre nœud il a le droit de faire passer le Wazer. Si une boucle est formée par une rue sans restriction et une rue privée, ou encore une rue à sens unique, il se pourrait que l'application suggère alors de passer par la rue privée ou même à contre sens, car pour lui peu importe le segment, du moment que l'on passe du nœud ID:12345 au nœud ID:54321 (par exemple). Si la boucle de deux segments est formée par un segment de 5m à droite et un détour de 30km à travers la forêt à gauche, il se pourrait même que le guidage indique de passer par la forêt. Merci d'éviter aux Wazers ce genre de situations loufoques et de toujours corriger les boucles à deux segments que vous trouvez. Ajoutez simplement un nœud en découpant l'un des deux segments en deux pour que la boucle soit formée de trois segments et que ce genre d'erreur de suggestion d'itinéraire ne puisse pas arriver. De manière générale on laissera intact le chemin le plus logique ou la route principale et on placera plutôt le nœud additionnel sur le segment privé, le parking, ou autre. (/!\ Attention cependant à ne pas créer de micro-segments) ====Boucle à un segment==== Cette erreur est beaucoup plus rare mais il arrive que des nouveaux éditeurs dessinent une boucle de manière à ce que le nœud A et le nœud B du même segment soient connectés l'un à l'autre. =====Boucles à un segment formant un détour===== Dans ces cas, il faut également ajouter suffisamment de nœuds pour que la boucle soit formée par au moins 3 segments. =====Boucles à un segment formant un demi-tour dans un cul-de-sac===== Pour ces cas précis, merci de supprimer la boucle (évtl. rond-point) et de vous référez à l'article sur les culs-de-sac ci-dessous. ==Culs-de-sac== Lorsqu'une rue est sans issue et se termine par une boucle ou un rond-point pour faire demi-tour. Merci de ne pas cartographier la boucle ou le rond-point. Veuillez à la place simplement tirer l'extrémité A ou B du segment jusqu'au point le plus éloigné possible à atteindre en roulant. Le serveur de navigation ayant la possibilité de suggérer d'aller au bout d'une rue et d'y faire demi-tour suffira à obtenir une instruction visuelle et audio exacte. Il n'est pas nécessaire de complexifier la carte ou de créer des boucles qui devront être formées de petits segments étant donné que toute boucle doit en contenir trois au minimum (voir l'article ci-dessus). En plus de ne pas permettre un calcul précis de l'ETA sur ce genre de construction, les instructions de navigation par défaut seraient le plus souvent étranges ou peu claires pour le Wazer. ==Type: Rue étroite, Ruelle (Narrow Street)== Le type ''Rue étroite, Ruelle'' a été introduit en 2018 à la demande de plusieurs communautés pour des cas spécifiques, ce type n'est pas uniquement visuel et applique une pénalité pour la navigation, c'est pourquoi il est important de ne pas l'utiliser n'importe comment. Certains pays ont d'ailleurs totalement interdit son utilisation, ce n'est pas le cas de la Suisse, cependant nous avons établi quelques règles à suivre: *'''Quand peut-on utiliser ce type en Suisse?''' - Lorsque: *#le segment est à double sens, et que *#le segment fait plus de 50m, et que *#le segment n'est assez large que pour un seul véhicule standard à la fois. *'''Quand ne doit-on pas utiliser ce type?''' - Lorsque: *#le segment est à sens unique, ou que *#le segment est un court passage sous voies ou un petit pont, ou que *#le segment est un cul-de-sac ou sert d'accès à une vallée en cul-de-sac ne pouvant pas servir de transit, ou que *#le segment est ou devrait être d'un autre type possédant déjà une pénalité (parking, privé etc...), ou que *#le segment empêche les croisements uniquement en présence d'un autocar, camion ou véhicule agricole, ou que *#le segment est réglementé par des feux tricolores permanents ou palettes de chantier (trafic en alternance), ou que *#le segment est étroit mais permet le croisement de véhicules standards, soit en roulant au pas soit par la présence de zones d'évitements, ou que *#le segment est un rétrécissement de la chaussée visant à réduire la vitesse (zones 20-40km/h) où les véhicules doivent se céder la priorité selon les panneaux et indications sur place, et finalement *#la cartographie de villages entiers avec ce type est interdite, ou doit impérativement faire l'objet d'une discussion sur le forum au préalable. *'''Autres cas''': Voir le sujet du forum sur les ''[https://www.waze.com/forum/viewtopic.php?f=63&t=225041#p1658955 '''routes à travers champs''']'' ==Notes== Ceci<nowiki> </nowiki>n'est qu'une liste subjective basée sur les erreurs les plus courantes. La lecture du Wiki et du forum reste une activité importante. Le Wiki Global<nowiki> </nowiki>est mis à jour fréquemment en fonction de l'arrivée des nouvelles fonctionnalités sur l'éditeur. Bien souvent ces nouveaux articles sont en anglais, faute de traduction dans les diverses langues, mais on peut très bien en parler sur le forum en français. fb6c6dd4cbb114a6e25bbd35ad3ec57b065502be 0 80 12083 12003 2019-07-15T21:50:56Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Diese Seite über die häufig gestellten Fragen in Waze sollte mit dem [http://www.waze.com/faq/ Official FAQ] und dem [http://www.waze.com/faq/technical_faq/ Technical FAQ] gelesen werden. Der [[Glossar|Glossar]] erklärt die Begriffe und die speziellen Bezeichnungen in Waze. =WME - Karteneditor= === Welche Browser werden vom Waze Map-Editor unterstützt? === Waze empfiehlt [http://www.google.com/chrome Google Chrome] Browser oder das [http://www.google.com/chromeframe Google Chrome Frame] Plugin mit dem Internet Explorer zu verwenden. Die Unterstützung für Microsoft Internet Explorer (IE) ist limitiert und manche Funktionen arbeiten evtl. nicht korrekt. Folgende Browser funktionieren mit dem Waze Map-Editor: *[http://www.google.com/chrome Chrome] (Empfohlen) *[http://www.apple.com/safari Safari] *[http://www.mozilla-europe.org/nl/firefox Firefox] === Was ist die Base-Map? === Die Base-Map ist eine Basis-Karte, die von Waze implementiert wurde. Die Base-Map ist in ihrer Rohform komplett unbearbeitet, das heisst: Es sind nur Straßen vorhanden und keine Straßen- oder Ortsnamen. Die Karte ist schlecht navigierbar und in der Regel müssen alle Straßen auch in ihrer Klassifizierung überprüft werden. Einbahnstraßen sind inexistent und auch alle Abbiegungen müssen erst noch gesetzt werden, bevor eine saubere Navigation möglich ist. Die Base-Map Straßen haben auch alle keine Fahrtrichtung. Deutschland ist beispielsweise ein Base-Map Land. === Was ist der Waze Map-Editor? === Der Waze Map-Editor oder "WME" ist der Name des Karteneditors.<br> Man kann sich anmelden unter:<br> https://www.waze.com/de/editor/ === Was sind Fahrten (Drives)? === "Drives" sind die Fahrten, die Du mit eingeschaltener Waze-App gemacht hast. Während der Fahrt speichert Waze die gefahrene Strecke (Ort, Zeit und Geschwindigkeiten) und überträgt diese Infos an den Server. Diese Daten validieren den bestehenden Zustand der Karte, lernen durchschnittliche Fahrzeiten ein (sogen. Segmentgeschwindigkeitsdaten) und lernen den Wazeservern gebräuchliche Wege. Die Benutzer oder Area-Manager, welche die Karte bearbeiten, können im Karteneditor die gefahrenen Strecken anhand anonymisierter GPS-Punkte sehen und die Straßen auf der Karte wenn nötig einzeichnen oder im Verlauf anpassen. Jeder Benutzer kann seine eigenen Fahrten unter "Fahrten" im Karteneditor anschauen. === Wann sehe ich meine Fahrten im Karteneditor? === Die Fahrten sind nach etwa einer Stunde im Waze Map-Editor sichtbar. Kurze Fahrten unter 50 Kilometer sind meist in weniger als 15 Minuten im Waze Map-Editor. Wenn die Server Probleme haben oder die Fahrten länger als 150 Kilometer sind, kann es sein, dass es bis zu einer Woche dauert. Sind die Fahrten nach einer Woche nicht vorhanden, sollte man dies via [https://world.waze.com/support/ Quick Help] auf der Support-Seite melden. Benutze den Mail-Link und beschreibe Dein Problem. Ein Blick auf die [http://status.waze.com/ Status Seite] oder ins [http://world.waze.com/forum Forum] kann auch hilfreich sein. === Was ist eine gesperrte Straße im Waze Map-Editor? (Lock)=== Die "Sperren" Funktion bewirkt folgendes: Ein gesperrtes Segment kann nicht durch Editoren mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]] bearbeitet werden. Der Rang eines Editors ermöglicht Ihm ein Segment mit einer "Bearbeitungssperre" (Lock) auf maximal seinem Editorenlevel zu versehen. Sinnvoll ist dies als Schutz bei wichtigen Hauptverkehrsadern wie Autobahnen (Freeway - Locklevel 5) oder Bundesstraßen (Locklevel 3). Gesperrte Segmente beeinflussen die Abbiegungen der Kreuzungen an den Enden der Segmente. Wenn eine Abiegung nicht geändert werden kann, ist möglicherweise ein Segment an der Kreuzung gesperrt. Zum entsperren der Segmente, richtet man eine Anfrage an das betreffende Forum. Es gibt Threads zum Thema Entsperren von Straßen.. Ausserdem kann oft ein L5/L6-Editor im Chat weiter helfen. Lies zum Thema "Sperren von Straßen" diese [[Sperren von Straßen (Locking)|Seite]]. ===Was ist das Penalty-System=== Für die Erstellung einer Route verwendet Waze unter anderem ein System von Penalties (Zeitzuschlägen). Das Penalty-System ist dafür verantwortlich, den schnellsten Weg zu finden. Es eliminiert mögliche Routen indem es für die Berechnung mehr Zeit (pro Segment oder Kreuzung) vergibt als erwartet.<br> Infos in deutscher Sprache findest Du auf dieser Seite: [[Wie Waze Routen kalkuliert]]<br> Infos in Englisch findest Du auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. Gib in unter "Stell eine Frage" der nanoRep Box das Wort "Penalties" ein.<br> ===Unterstützt Waze zeitlich begrenze Abbiegeverbote?=== Ja, Informationen dazu findest Du hier: [[Straßensperrungen und zeitlich beschränkte Fahrverbote]] =Waze-App= === Was bedeuten die kleinen Punkte auf den Straßen? === Dies sind Straßen, die noch nicht bestätigt wurden. Das heisst, dass diese Straßen noch nie befahren wurden, seit sie mit dem Karteneditor erstellt oder mit der Basis-Karte importiert wurden. Es kann sein, dass die Kreuzungen und die Geometrie nicht zu 100% korrekt sind, daher sollte man diesen Straßen Beachtung schenken. Wenn über solche Straßen gefahren wird, ändert sich das Waze-Icon auf dem Bildschirm und zeigt einen Pacman an der die Punkte verspeist. Dies gibt Punkte und bestätigt die Straße für Waze. Diese Straßen werden auch oft [[Glossar#Pacman_Roads.2C_Pacman_Stra.C3.9Fen|Pacman-Straßen]] genannt. Mehr dazu [[Ablauf_der_Aktualisierungsprozesse#Punkte_fressen.28Munching.2FPacman-Roads.29|hier]]. Die Punkte erhält nur, wer die Straße als erstes mit dem Pacman befährt. Die Straßen können noch länger unbestätigt erscheinen. === Was ist, wenn man beim Fahren keine Straße in der App sieht? === Wenn eine Straße befahren wird, die nicht in der App sichtbar ist, speichert Waze zwar die Routeninformationen wie gewohnt, fügt aber die Straße nicht ohne weiteres zum Karteneditor oder der Live Map hinzu. In diesem Fall kann man die Straße über die App [[Zeichne Straße auf |aufzeichnen]]. Die aufgezeichnete Straße erscheint rot in Waze und setzt auch an verschiedenen Stellen Kreuzungen, wo Waze z.B. eine Abbiegung während der Fahrt entdeckt. Wenn Waze wieder zurück auf eine vorhandene Straße kommt, sollte die Aufnahme automatisch pausieren. Man sollte diese Funktion nur verwenden, wenn auf Straßen gefahren wird, die noch nicht auf der Karte existieren! Waze zeichnet bei ungenauem GPS-Signal Straßen auf, wo schon welche vorhanden sind, da die Anwendung in diesem Fall der Meinung ist, dass man sich nicht auf einer existierenden Straße befindet. Dies führt zu unerwünschten Korrekturen durch die Editoren oder Area-Manager. Es ist auch zu beachten, dass Waze bei fehlender oder schlechter Netz-Abdeckung die Karte nicht in die Anwendung herunterladen kann. Das heisst: es ist keine Karte sichtbar, aber sie ist trotzdem bereits vorhanden. Auch in diesem Moment können Straßen aufgezeichnet werden. Daher Vorsicht bei der Aufzeichnung! === Ich habe neue Straßen aufgezeichnet - was nun? === Die neu aufgezeichneten Straßen erscheinen innerhalb kurzer Zeit im Karteneditor, wo Du diese weiter bearbeiten kannst. Bitte erledige dies innerhalb kurzer Frist, sonst wird die Karte nicht erweitert und die Benutzer können nicht von deiner Arbeit profitieren. Melde Dich dazu im Karteneditor an und bearbeite die Straßen. Details wie Straßenname, Stadt-/Gemeindename, Fahrtrichtungen, Straßentyp usw. sollten alle im Karteneditor ergänzt werden. Dabei sollte man die neue Straße mit bereits bestehenden verbinden und die Abbiegeverbote korrekt setzen. Ansonsten kann die Straße nicht oder nicht richtig bei der Navigation berücksichtigt werden. === Wann sehe ich meine Straßen in der Waze-App? === Das normale Verfahren ist, dass in regelmäßigen Abständen ein Aktualisierungsprozess auf den Servern ausgeführt wird (Stand 2019: 1-3x pro Woche). Wenn er beginnt, werden alle Edits bis zu diesem Zeitpunkt in den aktuellen Karten-Aktualisierungszyklus aufgenommen. Nachdem Aktualisierungszyklus komplett ist, werden die Daten in die Live-Map und die App geladen. Normalerweise wird die Aktualisierung auf der [http://status.waze.com/ Status Seite] veröffentlicht, mit dem Satz: "Enthält Edits bis..." Die Straßen werden in der Anwendung zwischengespeichert und nur aktualisiert, wenn eine der drei folgenden Bedingungen erfüllt ist: * Man sucht eine bestimmte Position auf der Karte aus dem Adressbuch. * Man navigiert durch die Straße. * Die Straße ist älter als eine Woche. Man kann auch die Aktualisierung über das Optionen Menü in der Waze Anwendung erledigen, bevor man losfährt. Die Aktualisierung ist auch abhängig davon ob die Karte seitens Waze aktualisiert wurde oder nicht. Das Datum der Live Map ist dabei massgebend. ===Warum sehe ich Meldungen, die hunderte Kilometer entfernt liegen auf der App=== Waze zeigt Dir mit einem Pop-Up nur die Verkehrsmeldungen innerhalb des definierten Radius um Deinen Standort an. Dies ist abhängig von den Einstellungen der Waze-App resp. des Radius den Du definiert hast. Der Radius schliesst deine Route mit ein, wenn Du mit Navigation unterwegs bist. Die Minimaldistanz zu Deinem Standort auf der Straße beträgt 5 Kilometer. ===Warum bewegen sich die Wazer auf der Karte nicht in Echtzeit?=== Andere Wazer sind auf der Karte der Waze-App sichtbar. Es besteht eine Verzögerung von 2-5 Minuten. Das hat mehrere Gründe: Sicherheitsgründe, Privatsphäre, Server-Kapazität und Netzwerk-Datenverkehr. Es wäre eine große Datenmenge erforderlich, um die Standorte aller Wazer im 2-Sekundentakt zu aktualisieren. ===Kann ich eine Verkehrsmeldung oder einen Unfall von zu Hause aus melden?=== Nein. Du kannst keine Meldungen irgendwo auf der Karte platzieren! Waze erlaubt nur Meldungen wie Polizei, Unfall, Gefahr, Blitzer etc. basierend auf Deiner ''aktuellen GPS-Position''. ===Kann ich anhand von Latitude und Longitude oder GPS Koordinaten navigieren?=== Ja. Im Suchfeld der Navigation ''Longitude, Latitude'' in Dezimalform eingeben Beispiel: United States, Disney's Epcot Center in Orlando, Florida findet man unter folgenden Koordinaten: "28.37529,-81.54942" Die Live-Map akzeptiert die selben Koordinaten auch im Suchfeld. ===Warum lernt Waze meine Routen nicht?=== Die Einstellung in der Waze-App "Lerne Fahrten zu häufigen Zielen" kann irreführend sein. Waze lernt nur Deine häufigen Ziele und wenn diese Einstellung im Menü aktiviert ist, erscheint ein Pop-Up, das dich nach Deinem Fahrziel fragt. Waze wählt die Route anhand der Einstellungen in der App , der Geschwindigkeiten und den vorhandenen Echtzeit-Verkehrsdaten entsprechend der aktuellen Tageszeit aus. Wenn Waze nicht die von Dir erwartete Route anbietet, kann dies auch an falschen Geschwindigkeiten in den Segmenten liegen. Waze braucht exakte Geschwindigkeiten aller Segmente im Umfeld Deiner Route, damit die Berechnung richtig funktioniert. ===Erhalte ich Punkte bei fehlender oder schlechter Datenverbindung?=== Damit Waze korrekt funktioniert muss eine ständige Datenverbindung bestehen. Bei Unterbrechung der Mobilfunkverbindung wird Waze versuchen Daten für Verkehrs-Meldungen und Gefahren vom Server zu erhalten, wird aber nicht in der Lage sein, zuverlässige Informationen zu liefern. Im Bezug auf die Punkte sammelt Waze Daten während der Zeit, in der eine Verbindung besteht (auch bei kleineren Unterbrechungen). Damit diese Daten (Punkte, Fahrten etc.) den Server erreichen, muss die App während oder am Ende der Fahrt die Daten zum Server hochladen können. Waze sendet die Daten an den Server, wenn die App heruntergefahren wird. Wenn während dem Herunterfahren der App keine Verbindung zum Server besteht, gehen alle Daten, die den Server noch nicht erreicht haben verloren. Punkte und Fahrten werden dann natürlich nicht gezählt. ===Wie ändere ich mein Land/Staat in der Waze-App?=== Normalerweise wird man dem Land oder Staat zugeordnet, in dem man sich mit Waze fortbewegt und die meisten Punkte innerhalb der letzten 1-3 Wochen gemacht hat. Bewegt man sich in vielen Ländern oder Staaten, kann man dies Waze mitteilen auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"] und der Heimatstaat oder das Heimatland wird von Waze fest zugeteilt. ===Ränge in der Waze-App=== Jeder Benutzer fängt als Baby-Wazer an. Die Tabelle zeigt an, wie du die Ränge emporsteigen kannst. [[Image:RankWazeSt.png | 450px |center]] {| border="1" align="center" style="text-align:center;" |[[Image:Wazer baby@2x.png |40px]] '''Baby Wazer''' |Willkommen in der Waze Welt. Wazer! Du bist jetzt ein Baby Wazer. Aber nicht für lange Zeit... Fahre 160 Kilometer um ein erwachsener Wazer zu werden. |- |[[Image:Happy@2x.png|40px]] '''Erwachsener Wazer''' |Du bist nun ein erwachsener Wazer und kannst dir deine Laune selbst aussuchen. Um ein Waze Krieger zu werden musst Du mehr Punkte machen... |- |[[Image:WazeWarrior.png|40px]] '''Waze Krieger''' |Beachte das Schild! Du hast die Top 10% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Dies beizubehalten wird nicht einfach sein... |- |[[Image:WazeKnight.png|40px]] '''Waze Ritter''' |Das Schwert gehört nun Dir! Du hast die Top 4% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Du bist fast ein Waze König... Halte Ausschau nach Möglichkeiten Punkte zu machen. |- |[[Image:KingWaze.png|40px]] '''Waze König''' |Du hast es geschafft! Du hast die Top 1% aller Wazer mit den höchsten Punktzahlen in deiner Region erreicht. Fahre in deiner Region herum wohl wissend, dass Du jetzt ein VIP bist... |} Um den königlichen Rang zu erreichen, musst du in den Top % von allen Wazern in deinem Land sein. In den USA wir dies nach Staaten berechnet. Die Top % werden einmal monatlich berechnet. Je mehr Wazer Punkte machen desto höher kann auch der Wert sein, den du erreichen musst um Schild, Schwert oder Krone zu erhalten. Dies kann zwar frustrierend sein, hilft aber zu garantieren, dass niemand die 'königliche' Ebene für immer hat - es gibt immer eine Chance für neue Wazer dies auch zu erreichen. =Dashboard und Echtzeit-Karte (Live-Map)= === Was ist das Dashboard? === Das [[Mein Dashboard|Dashboard]] ist die Seite, auf der alle persönlichen Konto Information und Statistiken zu finden sind wie: Punkte, gefahrene Strecken, usw.<br> Man kann sich anmelden unter:<br> https://www.waze.com/de/dashboard === Wann sind meine Straßen in der Live-Map zu sehen? === Dies sollte etwa aller 2-3 Tage geschehen. Wenn der visuelle Teil der Live Map nicht aktualisiert worden ist, sind die Änderungen dennoch vorhanden, sie sind zu sehen wenn man in die Karte klickt. Klickt man eine Straße an werden die kürzlich aktualisierten Daten angezeigt. Aktualisierungen der Karte in der Waze-App erscheinen zur gleichen Zeit. Das Datum des letzten Updates befindet sich links unterhalb der Live Map. dieses Datum ist auch für die Anwendung relevant. Neu aufgezeichnete Straßen sind erst in der Live Map zu sehen, wenn sie durch einen Editor bearbeitet wurden! =Punkte und Bonuspunkte= ===In welchem Zeitraum werden die wöchentlichen Punkte berechnet?=== Punkte werden von Montag bis Sonntag gezählt. Meldungen über die Top Drei werden normalerweise am Montag Morgen erscheinen. ===Wie werden die Punkte berechnet?=== Punkte werden nach der Anzahl der aktualisierten Segmente/Kreuzungen/anderer Objekte vergeben. Gefahrene Kilometer werden mit 3,2 Punkten (1 Meile = 5 Punkte) und 3 Beiträge im Forum mit 2 Punkten vergütet. Werden mehrere Segmente gleichzeitig geändert, wird nur 1 Punkt pro Segment vergeben. Du erhältst im gleichen Speichervorgang keine weiteren Punkte für das Ändern verschiedener Eigenschaften des gleichen Segments. Beispiel: Ändern der Segment-Ebene von 3 ausgewählten Segmenten (in einem Vorgang), gibt Dir 3 Punkte für die Änderung an 3 Segmenten. Straßennamen vergeben für unbenannte Segmente im selbigen Vorgang, kann in gewissen Fällen mehr Punkte geben. Eine Abbiegung verbieten oder zulassen zählt als eine Änderung der Abbiegung an der Kreuzung. Alle Änderungen an einer Kreuzung zählen nur ein einziges Mal. Es gibt keine weiteren Punkte für das mehrmalige Ändern der selben Abbiegung einer Kreuzung. Wird das gleiche Objekt mehrmals bearbeitet innerhalb von 24 Stunden, wird nur einmal ein Punkt pro Objekt in diesem Zeitraum gewährt. Werden größere Mengen an Änderungen gespeichert, erhältst Du nicht mehr als 150 Punkte pro Speichervorgang. Wenn Du mehr als 150 Änderungen auf dem Zähler des Karteneditors siehst, werden trotzdem nur maximal 150 Punkte pro Speichervorgang vergeben. Mehr Informationen zum Hintergrund der Berechnung gibt es: [http://www.waze.com/forum/viewtopic.php?f=14&t=10760&start=190 hier], oder auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. Suchbegriff: missing points. {| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1" |- ! Aktivität !! Punkte !! Einheit |- | Straßenberichte¹ || 6 || pro Meldung |- | Bericht kommentieren || 3 || pro Kommentar |- | Benzinpreise melden¹ || 8 || pro Meldung |- | Karten bearbeiten² || 1.5 || pro Bearbeitungsschritt³ |- | Aktualisierungsanfragen || 3 || pro gelöste Anfrage |- | Straßen benennen⁴ || 1 || pro Name |- | Hausnummer einfügen || 1 || pro Hausnummer |- | Foren Posts || 2 || pro 3 Posts |- | Road Goodies || 3-10 || pro Goodie |} {| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1" |- ! Aktivität !! pro Kilometer !! pro Meile |- | Normal fahren⁵ || 3.2 || 5 |- | Straßen fressen || 10 || 16 |- | Neue Straße aufzeichnen || 40 || 64 |} ¹ [[Der Waze Chat|Map-Chats]] und deren Kommentare geben keine Punkte. Damit Waze nicht zum Punkte sammeln misbraucht wird, sind die Meldungen zeitlich begrenzt. Dies gilt auch für die Preis-Meldungen an Tankstellen. ² Mehrfachbearbeitung (mehrere Straßen auswählen und bearbeiten) registriert alle obigen Änderungen separat, aber Änderungen an der Geometrie eines Segments, werden alle nur als eine Änderung an einem Segment angesehen. Beispiel: Mehrere Geometriepunkte an einem Segment verändern gibt nur 1 Punkt pro Segment. Der Karteneditor zählt Massenänderungen als eine "ungespeicherte Änderung" pro Massenänderung. Die Zahl, die Du im Zähler des Karteneditors siehst, ist nicht das Total der Punkte, die Du erhältst. ³ Im Moment werden zusätzliche Bonuspunkte für Karteneditoren vergeben. 300 Punkte pro 3000 Kartenbearbeitungen. Alle Änderungen werden zusätzlich mit 3 Punkten pro Änderung belohnt. ⁴ Neue Straßennamen geben nur Punkte, wenn das Segment nicht schon zuvor benannt war. ⁵ Mit oder ohne Navigation. === Bonuspunkte und weitere Bonbons=== Es gibt noch andere Möglichkeiten Punkte zu erhalten. In der Tabelle unten sind diese aufgeführt. Wenn Du Bonuspunkte erhältst, erscheint in der Waze-App eine Meldung, dass Du ein Bonbon auf Deiner Strecke findest. Fahre darüber und die Punkte werden Deiner wöchentlichen Statistik hinzugefügt. Die Bonbons erscheinen in der Regel an Feiertagen, wie z.B. zu Weihnachten, Ostern etc. Auf der Karte findest Du, je nach Feiertag, verschiedene Bonbons (Road Goodies), die Du überfahren und dafür die Punkte einsammeln kannst. Manchmal kann es sein, dass ein Bonbon nicht auf direktem Weg zu erreichen ist. Keine Sorge, das Bonbon erscheint nochmals, auch wenn Du Waze ein anderes Mal startest. Wenn Du die Anzeige der Bonbons in der Waze-App deaktiviert hast, werden die Punkte automatisch hinzugefügt. {| class="wikitable" style="background:none; font-size:75%; margin: 1em auto 1em auto" border="1" |- ! scope="col" width="200"| Aufgabe ! Punkte ! scope="col" width="200"| Bemerkungen |- | Deine ersten 16 Kilometer || 25 || |- | Deine erste Meldung || 25 || |- | Deine erste Meldung am Wochenende || 30 || |- | Erste Meldung eines Kartenfehlers || 50 || |- | Erster Freund || 200 || Dies kann nur erreicht werden, wenn Du Dich mit Facebook verbindest. Dein Freund muß auch mit Facebook verbunden sein. |- | Erste Woche¹ in der Du 2 Tage hintereinander gefahren bist || 100 || |- | Erste Woche¹ in der Du 3 Tage hintereinander gefahren bist || 200 || |- | Dein erster Edit auf der Karte || 200 || |- | Erste Woche¹ in der Du 4 Tage hintereinander gefahren bist || 300 || |- | Bearbeiten von 50 Kartenfehlern || 500 || |- | Wöchentlicher Top User in deinem Land || 500 || |- | 3000 Edits auf der Karte erledigt || 300 || Dies kann immer wieder erreicht werden. Bonbon kann auch erst erscheinen, wenn die Ränge auf dem Server aktualisiert wurden. |- | 800 Kilometer gefahren in einer Woche¹ || 1000 || |- | Fünf Freunde || 2000 || Siehe "Erster Freund" |- |} ¹ Die Punkte werden Montag bis Sonntag berechnet. Wenn Du der Meinung bist einen Bonus freigeschaltet zu haben, aber das Bonus-Bonbon auf der Straße nicht angetroffen hast, warte eine weitere Woche. Wenn es sich um einen Bonus handelt, der mehrere Tage benötigt um freigeschaltet zu werden, warte den Montag ab, denn der Kalender wird anfangs Woche am Montag zurückgesetzt. Das Bonus-Bonbon erscheint nicht, wenn Dein Bonus nicht zwischen Montag und Montag freigeschaltet wurde. Auch können einige Bonbons nicht in der gleichen Woche freigeschaltet werden, Du musst also eine weitere Woche abwarten. =Sonstiges= ===Wie kann ich mein Benutzerkonto löschen?=== Benutzerkonten können nicht gelöscht werden vom Benutzer, sende eine Anfrage auf der [https://world.waze.com/support/ Seite "Benutzerunterstützung"] mit Benutzernamen und registrierter E-Mail Adresse. ===Wie kann ich meinen Benutzernamen ändern?=== Ja. In der App unter "Account und Anmeldung" ===Wie eröffne ich ein Support Ticket/Anfrage an Waze?=== Das Forum ist ein primärer Kanal, um von der Community Hilfe zu erhalten. Einige Mitarbeiter von Waze beantworten auch manchmal Fragen, mehrheitlich zu Fehlern in der App oder WME. Wenn Du direkte Hilfe vom Support brauchst, gibt es ein Formular dafür: #Gehe zur [https://world.waze.com/support/ Seite "Benutzerunterstützung"]. #In der Quick Help Box, kannst Du Dein Problem eingeben im ersten Feld. #Ist Dein Problem nicht bekannt in der automatischen Hilfe, ''klick'' hier: '''"Still can't find what you're looking for? click here"''' Ein weiterer Dialog öffnet sich und Du kannst weitere Informationen finden. #Ist Dein Problem auch hier nicht beschrieben ''klick'' hier: '''"If you cannot find your answer, Please click here."''' #Füll das Formular aus mit allen Informationen, die benötigt werden, Permalinks aus dem Waze Map-Editor, Links zu App-Screenshots etc. in der More Details Box. #''Klick'' auf '''Submit''' Es wir keine Bestätigung an Dich gesendet, dass Dein Ticket eröffnet wurde, aber Du erhältst in der Regel in ein paar Tagen eine Antwort. [[Image:NanoRep-Box.png|center]] ===Wie lauten die Adressen der RSS Feeds für Waze?=== Hier findest du die [[RSS Feeds|Anleitung]] und eine Feed List. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 03a0adcf8199d753871e507d93bb48c85220e8d8 0 77 12084 12048 2019-07-28T17:48:53Z Vince1612 23 wikitext text/x-wiki ===== <big>'''Les règles de fermetures des signalements d'erreurs de carte (''UR - "Update Request"'') en Suisse sont les suivantes:'''</big> ===== '''Solved (corrigé)''' * '''Si''' '''vous pouvez''' '''identifier clairement la raison du signalement''' <u>et</u> que '''vous êtes capable de corriger le problème dans l'éditeur''', que '''vous parvenez à faire la modification''' <u>et</u> sauvegardez celle-ci correctement. Alors '''à ce moment vous pouvez marquer l'UR comme "corrigé"'''. Sinon, veuillez toujours fermer comme ci-dessous: <br> '''Not identified (non identifié)''' * Si pour plusieurs raisons, comme le manque de détails ou des conflits entre le tracé GPS et la route suggérée, vous ne parvenez pas à trouver la raison du signalement. Dans ces cas là, vous devriez tenter d'entrer en communication avec l'auteur du signalement. * Si une conversation a déjà été initiée par un autre éditeur et qu'un temps raisonnable a passé depuis les dernières informations fournies par l'auteur du signalement, vous pouvez laisser un message pour suggérer que l'UR soit fermé. Il est préférable d'attendre une réaction de l'autre éditeur avant de prendre action vous-même sur l'UR par courtoisie. * Si vous ne recevez pas de réponse dans un délai raisonnable après avoir posé des questions vous pouvez considérer l'option de fermer l'UR en non identifié.<br>Mais aussi, parfois des utilisateurs signalent des problèmes valides, mais qui ne peuvent pas être corrigés dans l'éditeur de carte. Ces signalement devraient eux-aussi être fermés comme non identifiés, avec une explication à l'auteur du signalement que le problème signalé ne peut pas ou ne sera pas corrigé dans l'éditeur. <br> '''Merci donc à tous de ne fermer les UR comme corrigé que si toutes les conditions citées ci-dessus sont remplies, et <u>ceci peu importe si la discussion dans le chat de l'UR a apporté une réponse ou une solution mais qu'aucune modification de carte n'a été effectuée.</u>''' ====== <br> <big>'''Pourquoi insister là-dessus?'''</big> ====== Outre le fait que de noter un UR comme corrigé sans avoir fait de modifications ou de corrections n'est pas approprié, vous devez prendre en compte que l'auteur de l'UR reçoit lui aussi des notifications du système immédiatement après une fermeture de son signalement. Un exemple de mail reçu lorsque l'UR est fermé comme corrigé: <br><blockquote><small>''Hi vince1612, <br><br><span style="color:#0000FF">The map issue you reported</span> from 11.09.2016 on Álafossvegur, Mosfellsbær ("Dead end. Concrete blocks blocking the road") <span style="color:#0000FF">was fixed by tbk0</span>. <br><span style="color:#0000FF">The map has been updated accordingly</span>. You've helped many wazers. Thanks!<br><br><span style="color:#0000FF">You can see the fixed area in the Waze map editor here</span> <nowiki>https://www.waze.com/editor/?zoom=5&lat</nowiki> ... 28&env=row''</small></blockquote><br><br>Essentiellement si on informe un utilisateur via le chat que son problème ne sera pas corrigé ou ne pourra pas l'être, ou même que l'on réponde à sa question mais toujours sans modifier la carte. Il est très <u>contradictoire</u> qu'il reçoive directement par la suite un message l'informant: * Que le problème qu'il a signalé a été résolu - <span style="color:red">faux</span> * Que la carte a été mise à jour - <span style="color:red">faux</span> * Qu'il a aidé beaucoup de Wazer et qu'il est remercié - c'est l'intention qui compte, mais <span style="color:red">faux</span> * Qu'il peut voir les corrections faites dans l'éditeur avec le permalink fourni - <span style="color:red">archi-faux</span> <br>D'autant plus que ceci est aussi ce qu'il reçoit sur son application en plus de l'e-mail. ===== Note sur le signalement "Mauvais sens de circulation" ===== En cas d'UR comprenant le titre ci-dessus, veuillez considérer la chose suivante: Le texte d'origine de ce signalement est "Wrong driving direction", ceci a causé pas mal de confusion lors de la traduction car en anglais le mot "direction" peut autant signifier '<nowiki/>''sens'' de circulation' qu'il peut signifier '''instruction'' de navigation ou de conduite'. Suivant la langue dans laquelle le Wazer utilise l'application Waze, il peut donc soit vouloir signaler une erreur dans le sens de circulation, soit vouloir signaler qu'il a reçu de mauvaises instructions de navigation/guidage pour une étape de son parcours ou pour sa destination finale. Il convient donc dans ces cas là d'entamer une discussion dans l'UR et de demander des précisions. Seul moyen de pouvoir être sûr. 1381ff34a9724d8a88efbdcbc64b51f24fa2fab0 0 12 12104 12069 2019-11-05T23:18:43Z Fuchserl 52 AT entfernt, weil hier nicht mehr aktuell und inzwischen auf eigener Seite wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. == Verwendete Abkürzungen == '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br> == Deutschland == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM !! AMS !! SME !! PM |- | top_gun_de||6||X||X||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- | BaseMapFrieder||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- | BellHouse||6||||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- | Durango48||6||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- | gordonski||5||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- | Gugi1968||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- | Hallenbach||5||||||X||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- | Jerec35||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- | MarcoSaxonia||5||||||||X||||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- | Mesonus||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- | Mynios||5||||E||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- | R66DE||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- | ''Raccoon_1 (inaktiv)''||''5''||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- | Snake68||6||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- | Tilonius||6||||||X||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- | tom-cat-67||6||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} == Schweiz == {| class="wikitable sortable center" |- ! User !! Edit-Level !! Koordinator !! GC !! LC !! CM!! AMS !! SME !! PM |- |- | popel22||6||X||X||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- | vince1612||6||||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- | svx-biker||6||||E||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- | pjw65||5||||||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- | Athannor||5||||||X||X||X||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- | cedricvondk||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- | Mal0ne||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- | MattKo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- | pikifoo||5||||||||X||||||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- | <span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>||||||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>|| |- | | | | | | | | | |} 812e7d5dc4404e61bc80226d460bc27cc2a76a86 12113 12104 2020-10-15T21:13:23Z Popel22 24 /* Schweiz */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. ==Verwendete Abkürzungen== '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br> ==Deutschland== {| class="wikitable sortable center" |- !User!!Edit-Level!!Koordinator!!GC!!LC!!CM!!AMS!!SME!!PM |- |top_gun_de||6||X||X||X||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=4751261 PM] |- |BaseMapFrieder||5|| || ||X||X|| ||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=11022664 PM] |- |BellHouse||6|| ||X||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=15538486 PM] |- |Durango48||6|| ||E||X||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=12238606 PM] |- |gordonski||5|| || ||X||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=2692079 PM] |- |Gugi1968||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13061920 PM] |- |Hallenbach||5|| || ||X||X|| ||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16784126 PM] |- |Jerec35||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16852375 PM] |- |MarcoSaxonia||5|| || || ||X|| ||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14701824 PM] |- |Mesonus||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=13786479 PM] |- |Mynios||5|| ||E||X||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3460659 PM] |- |R66DE||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16783423 PM] |- |''Raccoon_1 (inaktiv)''||''5''|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=5003774 PM] |- |Snake68||6|| || ||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3364498 PM] |- |Tilonius||6|| || ||X||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=6139645 PM] |- |tom-cat-67||6|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16854417 PM] |} ==Schweiz== {| class="wikitable sortable center" |- !User!!Edit-Level!!Koordinator!!GC!!LC!!CM!!AMS!!SME!!PM |- |- |popel22||6||X||X||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- |vince1612||6|| ||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- |svx-biker||6|| ||E||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- |pjw65||5|| || ||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- |Athannor||5|| || ||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- |cedricvondk||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- |Mal0ne||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- |MattKo||5|| || ||X||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- |pikifoo||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- |<span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>|| || ||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>|| |- | | | | | | | | | |} 52e58aaace85a5eb68707099759a93e83060b98e 12123 12113 2021-10-03T21:54:42Z Popel22 24 /* Deutschland */ wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. ==Verwendete Abkürzungen== '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br /> ==Schweiz== {| class="wikitable sortable center" |- !User!!Edit-Level!!Koordinator!!GC!!LC!!CM!!AMS!!SME!!PM |- |- |popel22||6||X||X||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- |vince1612||6|| ||X||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- |svx-biker||6|| ||E||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- |pjw65||5|| || ||X||X||X||X||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- |Athannor||5|| || ||X||X||X|| ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- |cedricvondk||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- |Mal0ne||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- |MattKo||5|| || ||X||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- |pikifoo||5|| || || ||X|| || ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- |<span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>|| || ||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>|| |- | | | | | | | | | |} bf2c6d12282ab634bfbadc45660abc78c0d4ccbd 12124 12123 2021-10-03T22:04:12Z Popel22 24 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. ==Verwendete Abkürzungen== '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager '''CM''': SM<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br /> ==Schweiz== {| class="wikitable sortable center" |- !User!!Edit-Level!!Koordinator!!GC!!LC!!CM!!AMS!!SME !SM!!PM |- |- |popel22||6||X||X||X||X||X|| | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- |vince1612||6|| ||X||X||X||X||X | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- |pjw65||5|| || ||X||X||X||X | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- |Athannor||5|| || ||X||X||X|| | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- |cedricvondk||5|| || || ||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- |Mal0ne||5|| || || ||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- |MattKo||5|| || ||X||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- |pikifoo||5|| || || ||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- |Blizteam |4 | | | | | | |x |[https://www.waze.com/forum/user_message_redirect.php?username=blizteam PM] |- |GeoCord |4 | | | | | | |x |[https://www.waze.com/forum/user_message_redirect.php?username=GeoCord PM] |- |Messanger |4 | | | | | | |x |[https://www.waze.com/forum/user_message_redirect.php?username=messanger PM] |- |svx-biker||6|| ||E||X||X||X|| | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- |<span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>|| || ||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span> | || |} ==== [[germany:Organisation_Deutschland|Seite für Deutschland]] ==== 6a91398e7eca9d5ecd16692fc6a2f3c5c5daa2c2 1 107 12105 2019-12-17T16:44:29Z Romain1228 54 devenir modificteur de carte wase wikitext text/x-wiki Bonjour, Je souhaiterais pouvoir changer la carte waze, pour aider la communauté. Cependant, si j'essaie de modifier, ajouter, etc quelque chose, lorsque je met sauvegarder, un message d'erreur me dit que je n'ai pas les autorisations pour faire des changement. Comment cela se fait-il ?? 6ed49e4ffbe4fdced9209828ce97d69daad6e210 0 5 12114 12063 2020-10-15T21:19:19Z Popel22 24 /* Straßen */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Einleitung== Wie Waze selbst ist diese Seite durch die Gemeinschaft entstanden und entwickelt sich kontinuierlich weiter. Viele hilfreiche Seiten existieren bereits unter [[Der Area Manager]], wie man den [[Der Waze Map-Editor|Karteneditor]] benutzt, Kartenfehler identifiziert und bearbeitet, Standards um Straßen zu klassifizieren und zu benennen und eine Seite über [[Häufig gestellte Fragen]]. Der Zweck dieser Seite ist es, Area-Managern und allen Benutzern zu helfen, eine Karte zu erstellen, welche für alle Waze-Endbenutzer während der Fahrt gut funktioniert. Auch kann so Mehraufwand durch nochmaliges Bearbeiten auf Grund von Fehlern oder Beschränkungen der Waze-Applikation vermieden werden. ==Anleitungen== Im Wiki finden sich zahlreiche Anleitungen. Das Wichtigste am Anfang ist daher, sich mit den Anleitungen auseinanderzusetzen. Also lies die [[Anleitung zum Bearbeiten der Karte]] sorgfältig, bevor Du die Karte bearbeitest. ==Hauptziele== ===Benutzerfreundlichkeit=== Wenn es um die Karte geht, ist das oberste Gebot: Für den Waze-Benutzer eine einfache Karte zu erstellen, der einfach zu folgen ist auf dem kleinen Bildschirm. Die Anweisungen sollen klar und sinnvoll sein und nur dann erscheinen, wenn sie auch gebraucht werden. ===Einfachheit=== Es soll nicht jede einzelne Spur auf der Karte eingezeichnet werden. Dies führt häufig nur zu unnötiger Komplexität, unlogischen Anweisungen beim Navigieren sowie unübersichtlichen Verhältnissen auf der Karte und schlussendlich zu unnötiger Mehrarbeit beim Korrigieren. ===Erhaltung des bestehenden Zustandes=== Durch das Befahren der Straßen werden in den Segmenten Informationen gespeichert, wie z.B. die Geschwindigkeit, welche für das optimale Routing benötigt wird. Wenn ein Segment gelöscht wird, gehen diese Informationen verloren. Wenn an einem unübersichtlichen Gewirr von Segmenten gearbeitet wird, ist es die bessere Wahl, diese weiterzuverwenden, anstatt bestehende zu löschen und neu zu zeichnen. ==In der Praxis== ===In zwei Einbahnstraßen aufteilen oder nicht?=== Es ist selten eine gute Idee, eine Straße, die nur durch Ein- und Ausfahrten auf eine Autobahn oder Hauptverkehrsstraße verbunden ist, in zwei Einbahnen aufzuteilen. An einer Kreuzung müssen auch nicht die Einmündungen aufgeteilt werden. Kreuzungen werden dadurch unnötig kompliziert, auf dem Bildschirm ist nichts mehr richtig zu erkennen, und die Anweisungen bei der Navigation sind verwirrend oder unsinnig. <br />'''Eine Straße sollte in zwei Einbahnen aufgeteilt werden wenn:''' *Mindestens 5 Meter Abstand zwischen den Fahrspuren besteht. (Abgetrennt durch Beton, Blumentöpfe oder Beete, Bäume oder Grasflächen.) *Die GPS-Punkte liegen bei einer Zoomstufe von 100 Metern im Karteneditor genügend weit auseinander. <br />'''Eine Straße sollte nicht in zwei Einbahnen aufgeteilt werden wenn:''' *Eine nicht befahrbare Fläche von weniger als 5 Metern zwischen den Fahrspuren besteht. *Eine längere Abbiegespur zwischen beiden Fahrtrichtungen existiert. *Viele Straßen kreuzen, die nur auf die nächstliegende Fahrbahn führen. *Google Maps oder andere Karten die Straßen so anzeigen. ===Wie man zwei Einbahnen zu einer Fahrspur vereint=== Wer eine Straße in zwei Fahrspuren aufteilt, sollte auch verstehen, was alles dazugehört, dies rückgängig zu machen. Es gibt leider keinen einfachen Weg zwei getrennte Fahrspuren wieder in eine zweispurige Straße zurückzuwandeln. Deshalb sollte man sich das Aufteilen gut überlegen. Wenn man eine Straße antrifft, die nicht aufgeteilt sein sollte, erkennt man dies sehr gut an der Summe der Fehlermeldungen der User. Dort wo die meisten Meldungen liegen brennt es in der Regel. Danach beginnt die hohe Kunst der Karten-Chirurgie am Waze-Karteneditor. Folgende Schritte sind zu erledigen: #Löschen der einen oder anderen Seite inkl. der Segmente, die beide Straßen verbinden. #Alle verwaisten Kreuzungen entfernen. #Richtungsänderungen an der verbleibenden Straße vornehmen. #Alle Abbiegeverbote kontrollieren. #Verbinden inkl. Abbiegeverbote aller Straßen, die in die verbleibende Straße münden. #Sicherstellen, dass die verleibende Straße korrekt in beide Richtungen verbunden ist. #Die Geometrie der zweispurigen Straße in die Mitte korrigieren. <br />Damit man sich damit nicht zu viel Arbeit einheimst, sollte man vorher die richtige Straße auswählen, die verbleiben soll. Dies entscheidet man natürlich anhand der bereits verbundenen Segmente. Man kann auch übers Kreuz löschen damit man schneller vorwärts kommt. Nicht vergessen die verbleibende Straße wieder korrekt mit ihr selbst zu verbinden. ===Autobahnen und Anschlüsse=== Langstrecken-Navigation ist nicht möglich, wenn die Autobahnen nicht korrekt verbunden sind. Deshalb ist diesem Thema besondere Aufmerksamkeit zu widmen. Man kann sehr viel bewirken, wenn man diese korrekt erstellt. Besondere Überlegungen müssen bei eingeschränkt befahrbaren Straßen angestellt werden. Es kann bei unsorgfältiger Vorgehensweise auch mehr Schaden enstehen, als an normalen Quartierstraßen. ====Strassen==== Beschränkt zugängliche Straßen mit mehreren Spuren in beiden Richtungen, die durch ein Hindernis zwischen den Spuren abgetrennt sind und allein durch Rampen zugänglich sind, sollten fast immer in zwei Einbahnen aufgeteilt werden. Andere normale Straßen sollten meistens nicht aufgeteilt werden. ====Ein- und Ausfahrten==== Einfahrten sollten nach der Richtung in die sie führen benannt werden. Ausfahrten sollten nach der Ausfahrtnummer - wenn vorhanden - und auch der Beschilderung der Ausfahrten benannt werden. Dabei auch gleich die Verbindungen und Abbiegeverbote kontrollieren. *Es gibt in den länderspezifischen Wikis mehr Informationen zur Benennung. *Verstehe den Unterschied zwischen Ein- und Ausfahrten und ebenerdigen [[Abbiegespuren]] ====Über- und Unterführungen==== Erfahrungen haben gezeigt, dass es sinvoller ist einzelnen bestimmten Segmenten einen unterschiedlichen Level zu geben, als längeren Straßen die nicht durch Kreuzungen unterteilt sind. Autobahnen beispielsweise sollten generell auf Level 0 bleiben. Brücken die darüber führen Level 1. Über- oder Unterführungen sollten nicht Level 0 haben. Auch bei komplizierten Verzweigungen sollten die Levels den tatsächlichen Zustand widerspiegeln. Trifft man auf Segmente, die bereits im Level verändert wurden, muss man dem Drumherum besondere Aufmerksamkeit schenken, damit nicht fehlerhafte Levels entstehen an Straßen, die bereits korrekt erstellt wurden. In den meisten einfachen Fällen können Probleme beseitigt werden, wenn man den Level eines Segments ändert. Bei komplizierten Kreuzungen kann es hilfreich sein, eine Zeichung zu erstellen oder man schaut sich zuerst die höchst- oder tiefstliegendsten Segmente an, um sich Klarheit zu verschaffen. Gelegentlich kommt man auch an eine Kreuzung, wo die Levels auf den ersten Blick keinen Sinn ergeben. Es kann daher hilfreich sein, ein Segment durch eine Kreuzung zu unterteilen. Es bleibt dann zu hoffen, dass nicht jemand die Kreuzung löscht ohne sich vorher zu vergewissern, wieso die da ist. ====Ebenen in Strassen==== Egal welche Ebene eine Straße besitzt, wenn sie durch eine Kreuzung verbunden wird, wird die ganze Verzweigung navigierbar. Wenn man eine Über- oder Unterführung findet, die mit der darüber- oder darunterliegenden Straße durch eine Kreuzung verbunden ist, so ist diese Kreuzung zu löschen. Waze navigiert die Benutzer sonst von einer Brücke auf eine draunterliegende Straße (oder umgekehrt), was nicht sehr sinnvoll ist. Man vergewissert sich dabei zuerst, ob die Ebenen der kreuzenden Straßen und die Benennung der einzelnen Segmente gleich sind. Ansonsten kann die Kreuzung nicht gelöscht werden. Desweiteren kann man dies auch mit der Brücken-Funktion beheben. ====Brücken-Funktion==== Zwei Segmente, die über- oder unterführen auswählen und das Brückensymbol anklicken. Die beiden Segmente vereinen sich und der Level erhöht sich automatisch auf Level 1. Falls damit kein Erfolg erzielt wird muss man allf. die Segmente einzeln abtrennen und neu verbinden. Verbindest Du mit der Brücken-Funktion Segmente, die unterschiedliche Levels besitzen, erhöht sich der Level um einen höher, als das Segment mit dem höchsten Level. ====Für Normalverkehr gesperrt oder zeitlich beschränkte Fahrverbote==== Inzwischen unterstützt Waze auch [[Straßensperrungen und zeitlich beschränkte Fahrverbote|zeitlich beschränkte Fahrverbote]], Richtungswechsel zu bestimmten Zeiten oder Straßen, die für bestimmte Fahrzeuge reserviert sind. Diese Straßen haben manchmal eigene Einfahrten und führen parallel entlang normaler Straßen. Das Routing kann dadurch Anweisungen geben, die falsch sind oder gar tödlich enden können! Die einfachste Lösung war bisher, diese Straßen zu löschen, falls sie bereits erstellt wurden. Dies ist jedoch nicht erwünscht. Daher ist es sinnvoll, die erweiterten Eigenschaften möglichst überall hinzuzufügen. ===Wann sind Ramps an Kreuzungen zu verwenden=== Siehe hier [[Abbiegespuren]] ===Wann ein Kreisverkehr erstellt werden soll=== Wenn klar ist, wie man [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehre]] erstellt, ist es die richtige Zeit alle Kreisel, die nur aus einzelnen Straßen Segmenten gezeichnet wurden auszutauschen und durch richtige Kreisverlehre zu ersetzen. Das gleiche gilt für Kreisverkehre der Basis-Karte (Base Map), die ganz leicht an ihrer seltsam eckigen Form erkannt werden können. Spätestens nach dem Korrigieren wird einem klarwerden, wie die [[Erstellen und bearbeiten eines Kreisverkehrs|korrekten Ansagen]] bei der Navigation zustandekommen. ===Richtung und Sperren von Straßen=== '''Wozu sperrt man Segmente?''' Die "Sperren"-Funktion bewirkt gem. [[Häufig gestellte Fragen#Was ist eine gesperrte Straße im Waze Map-Editor.3F|den Häufig gestellten Fragen]] folgendes: *Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]]. *Zwingt das Routing, den verbundenen Segmenten zu folgen und macht es nahezu unmöglich, gegen die definierte Fahrtrichtung zu Routen. '''Wann sperrt man Segmente?''' ''[[Wichtig: Unvollständige Segmente werden nicht gesperrt.]]'' Grundsätzlich bleiben Straßen frei. Waze lebt von den Beiträgen vieler, und jeder soll die Möglichkeit behalten, aktuelle Änderungen an Straßen schnell und einfach einzutragen. Sperren sollten also nur auf wichtigen Straßen vorgenommen werden, wo durch die Bearbeitung durch Einsteiger gravierende Auswirkungen, insbesondere auf den überregionalen Verkehr zu befürchten sind. Folgende Straßen müssen gelockt werden, wenn sie vollständig bearbeitet sind: *Autobahnen samt den zugehörigen Auf- und Abfahrten: Level 4 oder 5 *Bundesstraßen: Level 3 Wenn diese Straßen durch einen Editor niedrigen Ranges erstellt oder bearbeitet wurden, fordert er die Sperrung mit dem richtigen Level im Forum an. '''Informiere Dich in den länderspezifischen Wikis über die Gegebenheiten im betreffenden Land!''' ===Konnektivität=== Nur weil sich zwei Segmente an einer Kreuzung berühren, heißt dies noch nicht, dass sie auch korrekt miteinander verbunden sind. Abbiegeverbote kontrollieren! ===Unnötige Kreuzungen=== Unnötige Kreuzungen sind zu entfernen, da sie oft zu fehlerhaften Verbindungen und falschen Straßennamen führen. Zudem sind sie für das [[Wie Waze Routen kalkuliert|Routing]] nicht von Vorteil, da pro Kreuzung ein Zuschlag von 5 Sekunden zur Fahrzeitberechnung addiert wird. Ausnahmen bilden Orts- oder Landesgrenzen, oder wenn man in Kürze eine Straße mit einer Kreuzung verbindet. Wenn Kreuzungen entfernt werden, muss darauf geachtet werden, dass die Segmente die gleichen Eigenschaften besitzen. Andernfalls kann die Kreuzung nicht entfernt werden. Kreuzungen auf Straßen mit der Eigenschaft "Unbekannt" können aus Sicherheitsgründen nicht gelöscht werden. Straßen in Richtung ändern und nach dem Entfernen der Kreuzung allf. wieder auf "Unbekannt" setzen. ==Neue Straßen== ===Aufzeichnen mit der Waze-App=== Nach dem Aufzeichnen muss die Straße im Editor bearbeitet werden. Aufgezeichnete und unbearbeitete Straßen tauchen zwar in der App auf, sie werden aber nicht für das Routing benutzt. '''Man sollte diesen Anweisungen folgen:''' #Geometrie ausrichten anhand der Luftaufnahme, sofern diese am richtigen Ort ist in der Gegend. Dies sollte mit der Ebene GPS-Punkte geprüft werden. Kanten und Ecken abrunden wo nötig. #Korrekter Straßentyp und Name anhand der Definition des Landes einfügen. #Die korrekte Fahrtrichtung bestimmen. #Kreuzungen hinzufügen und Straßen korrekt verbinden. <br />Wenn mit dem Bearbeiten einer neuen Straße (rot) begonnen wird, wird die Straße ohne Typenänderung weiß erscheinen. Nach dem nächsten Kartenupdate von Waze, wird diese dann auf der Echtzeit-Karte und der Waze-App zu sehen sein. Daher ist es nicht sehr hilfreich, eine unfertige Straße zu hinterlassen. Solange sie rot ist, merkt mann noch, dass die Straße bearbeitet werden muss. Aber sobald sie weiß wird, kann sie im Karteneditor nicht mehr so schnell identifiziert werden. Wenn sie nur weiß ist und auch einen Straßennamen hat, mag dies gut aussehen, aber Waze weiß vielleicht noch nicht, dass die Straße befahren werden kann. ==Parkings und Parkplätze== Das Zuordnen eines Parkplatzes und dessen Straßen dient zwei Zwecken: *es erlaubt Waze eine Tür-zu-Tür-Navigation innerhalb des Parkplatzes *es erlaubt Waze von einer Hauptstraße weg zu navigieren, um fehlerhafte Verkehrsmeldungen zu vermeiden ====Gebrauch des "Parkplatz"-Straßentyps==== "Parkplatz" ermöglicht das Erstellen von Parkplätzen und verhindert gleichzeitig, dass der Routing-Server diese für die Navigation miteinbezieht. Damit nicht durch Parkplätze geroutet wird, hat Waze den Routing-Algorithmus im Juni 2012 geändert. Jedes Segment, das sich innerhalb eines Parkplatzes befindet ist daher als "Parkplatz" zu definieren. ====Einkaufszentren==== Wenn ein Parkplatz eines Einkaufszentrums erstellt wird, sollten Haupteinfahrten und die wichtigsten Verbindungen erstellt werden, Verbindungen zwischen verschiedenen Parzellen eines Parkplatzes und entlang der Geschäfte. Die meistgebrauchten Spuren sollten dabei miteinbezogen werden. Am wichtigsten sind hier Benutzerfreundlichkeit und Einfachheit. Es macht keinen Sinn, jedes einzelne Parkfeld mit einem Segment zu bestücken, dies lässt die Karte auf der App nur unübersichtlich aussehen. ====Kleinere Parkplätze==== Parkplätze, die einer kleinen Anzahl von Unternehmen dienen, sollten minimal sein. Genug, um dem Fahrer richtige Richtungen, Ein- und Ausfahrten zu zeigen und den Weg zu einem Geschäft. Manchmal reicht ein einziges paralleles Segment. ====Durchfahrts-Parkplätze==== Diese sollten nicht zu viele Einbahnen enthalten und am besten mit einer Einbahn als Schlaufe durch den Parkplatz führen. Man bedenke dabei, dass sich eine [[WME Schnellstart-Anleitung#Straßen-Schlaufen|Straße]] nicht mit sich selbst verbindet. ====Parkhäuser==== Wenn ein Parkhaus nur eine Ein- und Ausfahrt besitzt, sollte diese mindestens auf der Karte erscheinen. Ein einzelnes zweispuriges Segment reicht aus, da im Parkhaus meistens kein GPS-Signal vorhanden ist. Der Straßentyp ist "Parkplatz" und das Parkhaus kann mit einem Orientierungspunkt versehen werden. Besitzt das Parkhaus separate Ein- und Ausfahrten, so sollte eine Durchfahrt ermöglicht werden. Dazu reicht in den meisten Fällen ein einziges Segment. Es ist nicht nötig, jedes Stockwerk des Parkhauses darzustellen, dies macht die Karte nur unnötig unübersichtlich. ==Unterdrücken von Verkehrsmeldungen und Kartenfehlern== Straßensegmente vom Typ "Parkplatzstraße" verhindern die Erstellung von Staumeldungen, und von Kartenfehlern für "fehlende Straße". ==Klassifizierung von Kreuzungen== Verschiedene Arten von Kreuzungen haben [[Classification of crossings|Standard-Möglichkeiten]], um diese zu bearbeiten. Interessant sind auch diese Seiten:<br />[[Kreuzungen]]<br />[[Abbiegespuren]] <center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br />[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] b8f5931d9c60d3353b2c1a2f810763af8e9d285b 12115 12114 2020-10-15T21:20:15Z Popel22 24 /* Richtung und Sperren von Straßen */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Einleitung== Wie Waze selbst ist diese Seite durch die Gemeinschaft entstanden und entwickelt sich kontinuierlich weiter. Viele hilfreiche Seiten existieren bereits unter [[Der Area Manager]], wie man den [[Der Waze Map-Editor|Karteneditor]] benutzt, Kartenfehler identifiziert und bearbeitet, Standards um Straßen zu klassifizieren und zu benennen und eine Seite über [[Häufig gestellte Fragen]]. Der Zweck dieser Seite ist es, Area-Managern und allen Benutzern zu helfen, eine Karte zu erstellen, welche für alle Waze-Endbenutzer während der Fahrt gut funktioniert. Auch kann so Mehraufwand durch nochmaliges Bearbeiten auf Grund von Fehlern oder Beschränkungen der Waze-Applikation vermieden werden. ==Anleitungen== Im Wiki finden sich zahlreiche Anleitungen. Das Wichtigste am Anfang ist daher, sich mit den Anleitungen auseinanderzusetzen. Also lies die [[Anleitung zum Bearbeiten der Karte]] sorgfältig, bevor Du die Karte bearbeitest. ==Hauptziele== ===Benutzerfreundlichkeit=== Wenn es um die Karte geht, ist das oberste Gebot: Für den Waze-Benutzer eine einfache Karte zu erstellen, der einfach zu folgen ist auf dem kleinen Bildschirm. Die Anweisungen sollen klar und sinnvoll sein und nur dann erscheinen, wenn sie auch gebraucht werden. ===Einfachheit=== Es soll nicht jede einzelne Spur auf der Karte eingezeichnet werden. Dies führt häufig nur zu unnötiger Komplexität, unlogischen Anweisungen beim Navigieren sowie unübersichtlichen Verhältnissen auf der Karte und schlussendlich zu unnötiger Mehrarbeit beim Korrigieren. ===Erhaltung des bestehenden Zustandes=== Durch das Befahren der Straßen werden in den Segmenten Informationen gespeichert, wie z.B. die Geschwindigkeit, welche für das optimale Routing benötigt wird. Wenn ein Segment gelöscht wird, gehen diese Informationen verloren. Wenn an einem unübersichtlichen Gewirr von Segmenten gearbeitet wird, ist es die bessere Wahl, diese weiterzuverwenden, anstatt bestehende zu löschen und neu zu zeichnen. ==In der Praxis== ===In zwei Einbahnstraßen aufteilen oder nicht?=== Es ist selten eine gute Idee, eine Straße, die nur durch Ein- und Ausfahrten auf eine Autobahn oder Hauptverkehrsstraße verbunden ist, in zwei Einbahnen aufzuteilen. An einer Kreuzung müssen auch nicht die Einmündungen aufgeteilt werden. Kreuzungen werden dadurch unnötig kompliziert, auf dem Bildschirm ist nichts mehr richtig zu erkennen, und die Anweisungen bei der Navigation sind verwirrend oder unsinnig. <br />'''Eine Straße sollte in zwei Einbahnen aufgeteilt werden wenn:''' *Mindestens 5 Meter Abstand zwischen den Fahrspuren besteht. (Abgetrennt durch Beton, Blumentöpfe oder Beete, Bäume oder Grasflächen.) *Die GPS-Punkte liegen bei einer Zoomstufe von 100 Metern im Karteneditor genügend weit auseinander. <br />'''Eine Straße sollte nicht in zwei Einbahnen aufgeteilt werden wenn:''' *Eine nicht befahrbare Fläche von weniger als 5 Metern zwischen den Fahrspuren besteht. *Eine längere Abbiegespur zwischen beiden Fahrtrichtungen existiert. *Viele Straßen kreuzen, die nur auf die nächstliegende Fahrbahn führen. *Google Maps oder andere Karten die Straßen so anzeigen. ===Wie man zwei Einbahnen zu einer Fahrspur vereint=== Wer eine Straße in zwei Fahrspuren aufteilt, sollte auch verstehen, was alles dazugehört, dies rückgängig zu machen. Es gibt leider keinen einfachen Weg zwei getrennte Fahrspuren wieder in eine zweispurige Straße zurückzuwandeln. Deshalb sollte man sich das Aufteilen gut überlegen. Wenn man eine Straße antrifft, die nicht aufgeteilt sein sollte, erkennt man dies sehr gut an der Summe der Fehlermeldungen der User. Dort wo die meisten Meldungen liegen brennt es in der Regel. Danach beginnt die hohe Kunst der Karten-Chirurgie am Waze-Karteneditor. Folgende Schritte sind zu erledigen: #Löschen der einen oder anderen Seite inkl. der Segmente, die beide Straßen verbinden. #Alle verwaisten Kreuzungen entfernen. #Richtungsänderungen an der verbleibenden Straße vornehmen. #Alle Abbiegeverbote kontrollieren. #Verbinden inkl. Abbiegeverbote aller Straßen, die in die verbleibende Straße münden. #Sicherstellen, dass die verleibende Straße korrekt in beide Richtungen verbunden ist. #Die Geometrie der zweispurigen Straße in die Mitte korrigieren. <br />Damit man sich damit nicht zu viel Arbeit einheimst, sollte man vorher die richtige Straße auswählen, die verbleiben soll. Dies entscheidet man natürlich anhand der bereits verbundenen Segmente. Man kann auch übers Kreuz löschen damit man schneller vorwärts kommt. Nicht vergessen die verbleibende Straße wieder korrekt mit ihr selbst zu verbinden. ===Autobahnen und Anschlüsse=== Langstrecken-Navigation ist nicht möglich, wenn die Autobahnen nicht korrekt verbunden sind. Deshalb ist diesem Thema besondere Aufmerksamkeit zu widmen. Man kann sehr viel bewirken, wenn man diese korrekt erstellt. Besondere Überlegungen müssen bei eingeschränkt befahrbaren Straßen angestellt werden. Es kann bei unsorgfältiger Vorgehensweise auch mehr Schaden enstehen, als an normalen Quartierstraßen. ====Strassen==== Beschränkt zugängliche Straßen mit mehreren Spuren in beiden Richtungen, die durch ein Hindernis zwischen den Spuren abgetrennt sind und allein durch Rampen zugänglich sind, sollten fast immer in zwei Einbahnen aufgeteilt werden. Andere normale Straßen sollten meistens nicht aufgeteilt werden. ====Ein- und Ausfahrten==== Einfahrten sollten nach der Richtung in die sie führen benannt werden. Ausfahrten sollten nach der Ausfahrtnummer - wenn vorhanden - und auch der Beschilderung der Ausfahrten benannt werden. Dabei auch gleich die Verbindungen und Abbiegeverbote kontrollieren. *Es gibt in den länderspezifischen Wikis mehr Informationen zur Benennung. *Verstehe den Unterschied zwischen Ein- und Ausfahrten und ebenerdigen [[Abbiegespuren]] ====Über- und Unterführungen==== Erfahrungen haben gezeigt, dass es sinvoller ist einzelnen bestimmten Segmenten einen unterschiedlichen Level zu geben, als längeren Straßen die nicht durch Kreuzungen unterteilt sind. Autobahnen beispielsweise sollten generell auf Level 0 bleiben. Brücken die darüber führen Level 1. Über- oder Unterführungen sollten nicht Level 0 haben. Auch bei komplizierten Verzweigungen sollten die Levels den tatsächlichen Zustand widerspiegeln. Trifft man auf Segmente, die bereits im Level verändert wurden, muss man dem Drumherum besondere Aufmerksamkeit schenken, damit nicht fehlerhafte Levels entstehen an Straßen, die bereits korrekt erstellt wurden. In den meisten einfachen Fällen können Probleme beseitigt werden, wenn man den Level eines Segments ändert. Bei komplizierten Kreuzungen kann es hilfreich sein, eine Zeichung zu erstellen oder man schaut sich zuerst die höchst- oder tiefstliegendsten Segmente an, um sich Klarheit zu verschaffen. Gelegentlich kommt man auch an eine Kreuzung, wo die Levels auf den ersten Blick keinen Sinn ergeben. Es kann daher hilfreich sein, ein Segment durch eine Kreuzung zu unterteilen. Es bleibt dann zu hoffen, dass nicht jemand die Kreuzung löscht ohne sich vorher zu vergewissern, wieso die da ist. ====Ebenen in Strassen==== Egal welche Ebene eine Straße besitzt, wenn sie durch eine Kreuzung verbunden wird, wird die ganze Verzweigung navigierbar. Wenn man eine Über- oder Unterführung findet, die mit der darüber- oder darunterliegenden Straße durch eine Kreuzung verbunden ist, so ist diese Kreuzung zu löschen. Waze navigiert die Benutzer sonst von einer Brücke auf eine draunterliegende Straße (oder umgekehrt), was nicht sehr sinnvoll ist. Man vergewissert sich dabei zuerst, ob die Ebenen der kreuzenden Straßen und die Benennung der einzelnen Segmente gleich sind. Ansonsten kann die Kreuzung nicht gelöscht werden. Desweiteren kann man dies auch mit der Brücken-Funktion beheben. ====Brücken-Funktion==== Zwei Segmente, die über- oder unterführen auswählen und das Brückensymbol anklicken. Die beiden Segmente vereinen sich und der Level erhöht sich automatisch auf Level 1. Falls damit kein Erfolg erzielt wird muss man allf. die Segmente einzeln abtrennen und neu verbinden. Verbindest Du mit der Brücken-Funktion Segmente, die unterschiedliche Levels besitzen, erhöht sich der Level um einen höher, als das Segment mit dem höchsten Level. ====Für Normalverkehr gesperrt oder zeitlich beschränkte Fahrverbote==== Inzwischen unterstützt Waze auch [[Straßensperrungen und zeitlich beschränkte Fahrverbote|zeitlich beschränkte Fahrverbote]], Richtungswechsel zu bestimmten Zeiten oder Straßen, die für bestimmte Fahrzeuge reserviert sind. Diese Straßen haben manchmal eigene Einfahrten und führen parallel entlang normaler Straßen. Das Routing kann dadurch Anweisungen geben, die falsch sind oder gar tödlich enden können! Die einfachste Lösung war bisher, diese Straßen zu löschen, falls sie bereits erstellt wurden. Dies ist jedoch nicht erwünscht. Daher ist es sinnvoll, die erweiterten Eigenschaften möglichst überall hinzuzufügen. ===Wann sind Ramps an Kreuzungen zu verwenden=== Siehe hier [[Abbiegespuren]] ===Wann ein Kreisverkehr erstellt werden soll=== Wenn klar ist, wie man [[Erstellen und bearbeiten eines Kreisverkehrs|Kreisverkehre]] erstellt, ist es die richtige Zeit alle Kreisel, die nur aus einzelnen Straßen Segmenten gezeichnet wurden auszutauschen und durch richtige Kreisverlehre zu ersetzen. Das gleiche gilt für Kreisverkehre der Basis-Karte (Base Map), die ganz leicht an ihrer seltsam eckigen Form erkannt werden können. Spätestens nach dem Korrigieren wird einem klarwerden, wie die [[Erstellen und bearbeiten eines Kreisverkehrs|korrekten Ansagen]] bei der Navigation zustandekommen. ===Richtung und Sperren von Strassen=== '''Wozu sperrt man Segmente?''' Die "Sperren"-Funktion bewirkt gem. [[Häufig gestellte Fragen#Was ist eine gesperrte Straße im Waze Map-Editor.3F|den Häufig gestellten Fragen]] folgendes: *Verhindert die Bearbeitung von Segmenten durch Benutzer mit [[Rechte zum Bearbeiten der Karte|tieferen Rängen]]. *Zwingt das Routing, den verbundenen Segmenten zu folgen und macht es nahezu unmöglich, gegen die definierte Fahrtrichtung zu Routen. '''Wann sperrt man Segmente?''' ''[[Wichtig: Unvollständige Segmente werden nicht gesperrt.]]'' Grundsätzlich bleiben Straßen frei. Waze lebt von den Beiträgen vieler, und jeder soll die Möglichkeit behalten, aktuelle Änderungen an Strassen schnell und einfach einzutragen. Sperren sollten also nur auf wichtigen Strassen vorgenommen werden, wo durch die Bearbeitung durch Einsteiger gravierende Auswirkungen, insbesondere auf den überregionalen Verkehr zu befürchten sind. Folgende Straßen müssen gelockt werden, wenn sie vollständig bearbeitet sind: *Autobahnen samt den zugehörigen Auf- und Abfahrten: Level 4 oder 5 *Bundesstraßen: Level 3 Wenn diese Straßen durch einen Editor niedrigen Ranges erstellt oder bearbeitet wurden, fordert er die Sperrung mit dem richtigen Level im Forum an. '''Informiere Dich in den länderspezifischen Wikis über die Gegebenheiten im betreffenden Land!''' ===Konnektivität=== Nur weil sich zwei Segmente an einer Kreuzung berühren, heißt dies noch nicht, dass sie auch korrekt miteinander verbunden sind. Abbiegeverbote kontrollieren! ===Unnötige Kreuzungen=== Unnötige Kreuzungen sind zu entfernen, da sie oft zu fehlerhaften Verbindungen und falschen Straßennamen führen. Zudem sind sie für das [[Wie Waze Routen kalkuliert|Routing]] nicht von Vorteil, da pro Kreuzung ein Zuschlag von 5 Sekunden zur Fahrzeitberechnung addiert wird. Ausnahmen bilden Orts- oder Landesgrenzen, oder wenn man in Kürze eine Straße mit einer Kreuzung verbindet. Wenn Kreuzungen entfernt werden, muss darauf geachtet werden, dass die Segmente die gleichen Eigenschaften besitzen. Andernfalls kann die Kreuzung nicht entfernt werden. Kreuzungen auf Straßen mit der Eigenschaft "Unbekannt" können aus Sicherheitsgründen nicht gelöscht werden. Straßen in Richtung ändern und nach dem Entfernen der Kreuzung allf. wieder auf "Unbekannt" setzen. ==Neue Straßen== ===Aufzeichnen mit der Waze-App=== Nach dem Aufzeichnen muss die Straße im Editor bearbeitet werden. Aufgezeichnete und unbearbeitete Straßen tauchen zwar in der App auf, sie werden aber nicht für das Routing benutzt. '''Man sollte diesen Anweisungen folgen:''' #Geometrie ausrichten anhand der Luftaufnahme, sofern diese am richtigen Ort ist in der Gegend. Dies sollte mit der Ebene GPS-Punkte geprüft werden. Kanten und Ecken abrunden wo nötig. #Korrekter Straßentyp und Name anhand der Definition des Landes einfügen. #Die korrekte Fahrtrichtung bestimmen. #Kreuzungen hinzufügen und Straßen korrekt verbinden. <br />Wenn mit dem Bearbeiten einer neuen Straße (rot) begonnen wird, wird die Straße ohne Typenänderung weiß erscheinen. Nach dem nächsten Kartenupdate von Waze, wird diese dann auf der Echtzeit-Karte und der Waze-App zu sehen sein. Daher ist es nicht sehr hilfreich, eine unfertige Straße zu hinterlassen. Solange sie rot ist, merkt mann noch, dass die Straße bearbeitet werden muss. Aber sobald sie weiß wird, kann sie im Karteneditor nicht mehr so schnell identifiziert werden. Wenn sie nur weiß ist und auch einen Straßennamen hat, mag dies gut aussehen, aber Waze weiß vielleicht noch nicht, dass die Straße befahren werden kann. ==Parkings und Parkplätze== Das Zuordnen eines Parkplatzes und dessen Straßen dient zwei Zwecken: *es erlaubt Waze eine Tür-zu-Tür-Navigation innerhalb des Parkplatzes *es erlaubt Waze von einer Hauptstraße weg zu navigieren, um fehlerhafte Verkehrsmeldungen zu vermeiden ====Gebrauch des "Parkplatz"-Strassentyps==== "Parkplatz" ermöglicht das Erstellen von Parkplätzen und verhindert gleichzeitig, dass der Routing-Server diese für die Navigation miteinbezieht. Damit nicht durch Parkplätze geroutet wird, hat Waze den Routing-Algorithmus im Juni 2012 geändert. Jedes Segment, das sich innerhalb eines Parkplatzes befindet ist daher als "Parkplatz" zu definieren. ====Einkaufszentren==== Wenn ein Parkplatz eines Einkaufszentrums erstellt wird, sollten Haupteinfahrten und die wichtigsten Verbindungen erstellt werden, Verbindungen zwischen verschiedenen Parzellen eines Parkplatzes und entlang der Geschäfte. Die meistgebrauchten Spuren sollten dabei miteinbezogen werden. Am wichtigsten sind hier Benutzerfreundlichkeit und Einfachheit. Es macht keinen Sinn, jedes einzelne Parkfeld mit einem Segment zu bestücken, dies lässt die Karte auf der App nur unübersichtlich aussehen. ====Kleinere Parkplätze==== Parkplätze, die einer kleinen Anzahl von Unternehmen dienen, sollten minimal sein. Genug, um dem Fahrer richtige Richtungen, Ein- und Ausfahrten zu zeigen und den Weg zu einem Geschäft. Manchmal reicht ein einziges paralleles Segment. ====Durchfahrts-Parkplätze==== Diese sollten nicht zu viele Einbahnen enthalten und am besten mit einer Einbahn als Schlaufe durch den Parkplatz führen. Man bedenke dabei, dass sich eine [[WME Schnellstart-Anleitung#Straßen-Schlaufen|Straße]] nicht mit sich selbst verbindet. ====Parkhäuser==== Wenn ein Parkhaus nur eine Ein- und Ausfahrt besitzt, sollte diese mindestens auf der Karte erscheinen. Ein einzelnes zweispuriges Segment reicht aus, da im Parkhaus meistens kein GPS-Signal vorhanden ist. Der Straßentyp ist "Parkplatz" und das Parkhaus kann mit einem Orientierungspunkt versehen werden. Besitzt das Parkhaus separate Ein- und Ausfahrten, so sollte eine Durchfahrt ermöglicht werden. Dazu reicht in den meisten Fällen ein einziges Segment. Es ist nicht nötig, jedes Stockwerk des Parkhauses darzustellen, dies macht die Karte nur unnötig unübersichtlich. ==Unterdrücken von Verkehrsmeldungen und Kartenfehlern== Straßensegmente vom Typ "Parkplatzstraße" verhindern die Erstellung von Staumeldungen, und von Kartenfehlern für "fehlende Straße". ==Klassifizierung von Kreuzungen== Verschiedene Arten von Kreuzungen haben [[Classification of crossings|Standard-Möglichkeiten]], um diese zu bearbeiten. Interessant sind auch diese Seiten:<br />[[Kreuzungen]]<br />[[Abbiegespuren]] <center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br />[[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 5049917e57ae39dcf8fc18a6e27426a4b665f761 0 1 12116 12066 2021-10-03T21:24:45Z Popel22 24 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. *'''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone]. Hilfe und Anleitungen findest Du (vorerst nur auf englisch im [https://support.google.com/waze#topic=6273402 Help Center] *'''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] *'''Bitte nicht''' **an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast **[[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind **Strasse und Orte benennen bis Du [[Strassen und Orte benennen in der Schweiz]] gelesen hast *'''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] Als Neu-Editor kannst du dir [https://docs.google.com/presentation/d/19cGlE4UCKz2latquEac_ZnaKAYXR-mGxqigYL1hUkow/edit#slide=id.p14 hier] eine kurze Präsentation ansehen, um erste Grundlagen zu erlernen *'''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: *[[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> *[[Strassen und Orte benennen in der Schweiz]] *[[Kartenlegende Schweiz]] *[[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> *[[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] *[[Der_Area_Manager|Area-Manager]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> *Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. *Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse *Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] *Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] *Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> *[[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" |[[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 857c302541166690ac134386e3ada5d8b9315d0b 12120 12116 2021-10-03T21:42:34Z Popel22 24 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. *'''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone]. Hilfe und Anleitungen findest Du (vorerst nur auf englisch im [https://support.google.com/waze#topic=6273402 Help Center] *'''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] *'''Bitte nicht''' **an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast **[[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind **Strasse und Orte benennen bis Du [[Strassen und Orte benennen in der Schweiz]] gelesen hast *'''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] Als Neu-Editor kannst du dir [https://docs.google.com/presentation/d/19cGlE4UCKz2latquEac_ZnaKAYXR-mGxqigYL1hUkow/edit#slide=id.p14 hier] eine kurze Präsentation ansehen, um erste Grundlagen zu erlernen *'''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: *[[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> *[[Strassen und Orte benennen in der Schweiz]] *[[Kartenlegende Schweiz]] *[[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> *[[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] *[[Der_Area_Manager|Area-Manager (AM)]] *State-Manager (SM) </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> *Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. *Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse *Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] *Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] *Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> *[[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" |[[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] 3efd4c1aab27b329cb57f663312b8de6c57a217d 12122 12120 2021-10-03T21:50:20Z Popel22 24 wikitext text/x-wiki <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:120%"> <big>'''Komplette Anleitung für Waze in der Schweiz (in ständiger Bearbeitung)'''</big></p></div> <br> [[Image:swazer.png|300px|center]] <br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:110%">Pour les romands ( ''suisses francophones'' [[File:Drapeau_FR.png | 35px]] ) </p> '''Veuillez suivre le lien suivant pour obtenir des [[Informations en français]]'''. </div> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Was ist Waze und wie geht's los?</p> <div style="padding:5px"> Waze ist eine kostenlose GPS-Navigationsanwendung mit Sprachausgabe, durch die Benutzer generierte Kartenupdates und Verkehrsinformationen in Echtzeit.<br />[[Die soziale Vernetzung|Die soziale Vernetzung]] ist dabei ein weiterer Bestandteil von Waze. *'''Hol Dir''' die kostenlose [http://world.waze.com/ Waze-Anwendung für dein Smartphone]. Hilfe und Anleitungen findest Du (vorerst nur auf englisch im [https://support.google.com/waze#topic=6273402 Help Center] *'''Verstehe''' den [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] *'''Bitte nicht''' **an der Karte arbeiten bis Du [[Die beste Vorgehensweise beim Bearbeiten der Karte]] gelesen hast **[[Zeichne Straße auf]] anschalten, wenn Du auf Strassen fährst die schon vorhanden sind **Strasse und Orte benennen bis Du [[Strassen und Orte benennen in der Schweiz]] gelesen hast *'''Alles''', was Du wissen musst, steht hier drin: [[Anleitung zum Bearbeiten der Karte]] Als Neu-Editor kannst du dir [https://docs.google.com/presentation/d/19cGlE4UCKz2latquEac_ZnaKAYXR-mGxqigYL1hUkow/edit#slide=id.p14 hier] eine kurze Präsentation ansehen, um erste Grundlagen zu erlernen *'''Beteilige Dich''' im [[Diskussionsforum|Ankündigungs- und Diskussionsforum]] </div></div><div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Bearbeiten der Karte mit dem Waze Map-Editor</p> <div style="padding:5px"> Waze Map-Editor Anleitung: *[[Anleitung zum Bearbeiten der Karte]] </div></div><br> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Strassen und Orte benennen in der Schweiz</p> <div style="padding:5px"> *[[Strassen und Orte benennen in der Schweiz]] *[[Kartenlegende Schweiz]] *[[Ortsliste Schweiz]] **[http://www.waze.com/forum/viewforum.php?f=63&sid=f7ad225e81fd5a2ed3dff790b9aff6b3 Forum Schweiz] </div></div> <br /> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Rollen / Funktionen</p> <div style="padding:5px"> *[[Organisation_DACH|Übersicht der Country Manager (CM) DACH]] *[[Der_Area_Manager|Area-Manager (AM) und State Manager (SM)]] </div></div> <br /> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Du hast ein Problem und suchst eine Lösung</p> <div style="padding:5px"> *Lese hier im Wiki nach. Es gibt auch ein Suchfeld oben links. *Orientiere Dich auf der [http://status.waze.com/ Status Seite] über aktuelle Ereignisse *Benutze das [http://world.waze.com/forum Forum] und die [http://www.waze.com/forum/search.php Foren-Suchfunktion] *Bevor Du eine Frage stellst lies das hier: [[Wann stelle ich ein Frage im Forum]] *Benutze die Quick Help auf der [http://world.waze.com/support/ Support Seite] <br> '''Wenn alles fehl schlägt''', frage den Waze Support per [[Mail an den Support|E-Mail]] </div></div> <br /> <div style="border:thin solid lightblue"> <p style="margin:0;padding:2px;background:#B0E2FF;border:thin solid lightblue;font-weight:bold;font-size:100%"> Sonstiges</p> <div style="padding:5px"> *[[Technical Information]] Credit to argus-cronos, svx-biker and pikifoo de la suisse romande for keeping the Swiss Wiki alive, swiss wazer pic on top from Caradellino, thanks to Austrian Community. </div></div> <br> {| border="0" align="center" width="100%" style="background:#e6ecf3" |- | style="width:33%" align="left" |[[Image:b.gif]] [http://status.waze.com/ Informiere dich auf der Status Seite über aktuelle Ereignisse] |} For instructions on editing the map in your country and help in using Waze, in your language, choose from: {{Countries}} [[Category:Schweiz]] c3aa73c65591bbf21ab869a94090ba318b7282d7 0 8 12117 12045 2021-10-03T21:30:40Z Popel22 24 /* Anleitung zum Bearbeiten der Karte */ wikitext text/x-wiki ==Anleitung zum Bearbeiten der Karte== Hier findest Du die komplette Anleitung zum Bearbeiten der Karte und alle wichtigen Links, die Dir das geduldige Leben mit Waze erleichtern sollen. Im deutschsprachigen Raum gibt es Wiki-Seiten für verschiedene Länder. Bitte beachte die jeweiligen Regeln wenn Du ausserhalb der Schweiz editierst : *[https://wazeopedia.waze.com/wiki/Austria Wiki für Österreich] *[https://wazeopedia.waze.com/wiki/Germany Wiki für Deutschland] *[https://wazeopedia.waze.com/wiki/Switzerland Wiki für die Schweiz] ==Waze Map-Editor Anleitung== *[[Der Waze Map-Editor|Der Waze Map-Editor "WME"]] *[[WME Schnellstart-Anleitung]] *[[WME Update Requests]] *[[WME Map Problems]] *[[WME Hausnummern]] ==Wichtiges zum Thema Kartenbearbeitung== *[[Die beste Vorgehensweise beim Bearbeiten der Karte]] *[[Rechte zum Bearbeiten der Karte]] *[[Sperren von Straßen (Locking)]] *[[Soft und Hard Turns]] *[[Kreuzungen]] *[[Abbiegespuren]] *[[Abbiegeanweisungen über Pfeile]] *[[Erstellen und bearbeiten eines Segments]] *[[Erstellen und bearbeiten eines Kreisverkehrs]] *[[Orte und Navigationspunkte]] *[[Unterführungen und Brücken]] *[[Fußwege und Privatstraßen]] *[[Straßensperrungen und zeitlich beschränkte Fahrverbote]] *[[Verstreute Orte]] *[[Der Area Manager]] ==Seiten auf Englisch== Wenn Ihr genauer wissen wollt wie Waze funktioniert, sei Euch der Technische Teil ganz unten im [[global:Main_Page|Global Wiki]] ans Herz gelegt ==Problemlösung== *[[Häufig gestellte Fragen]] *[[Ablauf der Aktualisierungsprozesse]] *[[Wie Waze Routen kalkuliert]] *[[Mein Dashboard]] *[[Die Server Bänke]] *[[Der Debug Mode]] (veraltet) *[[Wann stelle ich ein Frage im Forum]] *[[Hilf mit die Karte zu vervollständigen]] *[[Mail an den Support]] *[[Diskussionsforum]] *[[Glossar]] (oder lieber [[usa:Glossary|glossary]] ? ) *[[Privatsphäre]] (im Aufbau) *[[Suchcodes]] ==Sonstige Links== *[[Zeichne Straße auf]] (veraltet) *[[Die soziale Vernetzung]] *[[Der Waze Chat]] *[[RSS Feeds]] *[[Feed List]] [[Category:Anleitung]] b06c393122acbd95839062c62f7077745dedaa60 0 2 12118 12041 2021-10-03T21:35:26Z Popel22 24 wikitext text/x-wiki *[[Diskussionsforum]] *[https://join.slack.com/t/wazedach/shared_invite/zt-8n7zglck-LQB1VS5QSmGideMm2hP52w Waze DACH Slack Channel] *[[Der Waze Chat]] *[http://www.waze-switzerland.ch/ inoffizielle schweizer Homepage] *[[Facebook]] *[http://www.waze.com/blog/ Waze Blog] * <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] ea4cdd1d21e04b7d3ecdd622217ba8b7e7268e2a 0 13 12119 11990 2021-10-03T21:40:01Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für den AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' *Für die Wazer in seiner Region im '''Forum''' verfügbar sein. *Den Editoren seiner Gegend Hilfestellung leisten. *Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' *'''Update-Requests''' bearbeiten. *'''Map-Problems''' bearbeiten. *'''Blitzer''' überprüfen. ==Anmeldung Area-Manager== Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Schon recht sattelfest in den Editier-Regeln sein *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:''' *Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. *Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. *Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. *Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. *Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. *Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". *Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. *Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für die Schweiz:''' *vince1612 *popel22 *pjw65 ===Richtlinien, die Du genau kennen solltest!=== '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. ===Online-Formular=== Folgendes musst Du tun: *Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. *Klicke auf [[WME Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. *Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. *Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==AM-Liste== Wenn du AM geworden bist, erscheinst du in der AM-Liste deines Landes: *[https://docs.google.com/spreadsheets/d/1JadJCU3K8U3oCzRvDy--DI2cnztT2l_PkMgoWoR1N38/edit?usp=sharing Deutschland] *Österreich (kommt bald) *Schweiz (kommt bald) ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] a37cf659c3d73f8432a8296e23c98bb24fe3d7f0 12121 12119 2021-10-03T21:45:37Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] ==Was macht ein Area-Manager== Der Area-Manager (AM) betreut ein bestimmtes von ihm ausgewähltes Gebiet. In der Regel wird man da AM, wo man sich am besten auskennt, um ein Gebiet optimal zu betreuen. Dies kann aber auch abweichen. <br> Sein AM-Gebiet ist immer als ganzes für den AM zum Bearbeiten freigeschaltet, der AM untersteht aber den normalen Sperr-Regeln (sprich: er kann nur Segmente bis zu seiner Stufe bearbeiten, wie alle). '''Kurz zusammengefasst sind die Aufgaben:''' *Für die Wazer in seiner Region im '''Forum''' verfügbar sein. *Den Editoren seiner Gegend Hilfestellung leisten. *Sein betreutes Gebiet im Auge behalten. '''Wichtige Arbeiten ausführen wie:''' *'''Update-Requests''' bearbeiten. *'''Map-Problems''' bearbeiten. *'''Blitzer''' überprüfen. ==Anmeldung Area-Manager== Auf dieser Seite findest Du das Anmeldeformular, um Area-Manager im [[Glossar#DACH|DACH-Raum]] zu werden. Dieses Vorgehen gilt für Deutschland, Österreich und die Schweiz, welche die Selbstverwaltung für Area-Manager gemeinsam betreiben. Als Area-Manager solltest Du auf jeden Fall das Wiki gelesen haben und kennen. '''Als Richtwert solltest Du - um Area-Manager zu werden - mindestens:''' *500 sinnvolle Kartenbearbeitungen (Edits) gemacht haben *Schon recht sattelfest in den Editier-Regeln sein *Ein paar Beiträge im Forum geschrieben haben *Mindestens 1 Monat bei Waze angemeldet sein *Bei Anfrage eines Country-Managers einen Screenshot Deines Dashboards senden und Permalinks von den Gebieten, die Du bereits bearbeitet hast. '''Beachte:''' *Die Anmeldung mit dem Formular ist die einzige Möglichkeit, um Area-Manager zu werden. *Du kannst alle Straßen bearbeiten, die nicht von Editoren mit höherer Stufe gelockt wurden. Wende Dich mit Unlock-Requests an die Benutzer im Forum Deiner Community, jedes Land hat Threads dafür. *Fragen kannst Du jederzeit im betreffenden Forum oder per PM stellen. Bedenke, daß die Community freiwillig bei Waze mitmacht, es kann daher sein, dass Du nicht sofort eine Antwort erhältst. *Deine Anfrage wird von den [[Glossar|Country-Managern]] bearbeitet und an den Waze-Support weitergeleitet. *Du musst über PM / E-Mail erreichbar sein und Dich im Forum beteiligen. *Bitte trage im Formular Deinen vollständigen Waze-Benutzernamen ein, nicht den "Nickname". *Wenn Du eine Anfrage gesendet hast, wird ein Country-Manager innerhalb 24 Stunden mit Dir Kontakt aufnehmen. *Nach erfolgreicher Kontaktaufnahme, wird Deine Anfrage an den Support weitergeleitet, der das gewünschte Gebiet erfasst. Informationen zur Führung der Selbstverwaltung findest Du [http://world.waze.com/forum/viewtopic.php?f=74&t=44479 hier]. '''Selfmanagement-Team für die Schweiz:''' *vince1612 *popel22 *pjw65 ===Richtlinien, die Du genau kennen solltest!=== '''Mit dem Versenden des Formulars, erklärst Du dich damit einverstanden, die Wiki-Standards, die durch die Community in Deinem Land definiert wurden einzuhalten. Solltest Du Fragen haben, wende Dich bitte an die Community in Deinem Land, wir sind im [https://www.waze.com/forum/viewforum.php?f=24 DACH-Forum] jederzeit bereit Dir zu helfen.''' Wenn Du nicht nach den Richtlinien arbeitest, kannst Du jederzeit herabgestuft oder gar aus Waze ausgeschlossen werden. Wenn Du nicht erreichbar bist und auf persönliche Nachrichten nicht antwortest, wirst Du herabgestuft und Deine AM-Rechte werden Dir entzogen. Dies gilt vor allem im Umgang mit den Country-Managern Deines Landes. Wir dulden keinen Vandalismus. ===Online-Formular=== Folgendes musst Du tun: *Benutze den [[Der Waze Map-Editor|Karteneditor]], positioniere die Karte und setze die '''Zoomstufe''' so, dass das Gebiet angezeigt wird, das Du managen willst. *Klicke auf [[WME Oberfläche und Steuerelemente#Die Permalink Schaltfläche|Permalink]] und kopiere die Adresse aus der Adressleiste deines Browsers. *Die Adresse ist dann in dieses [https://docs.google.com/spreadsheet/viewform?formkey=dEU4WlF3ZTdOLTJ6WTBEMi14SDFhUVE6MA#gid=0 Online-Formular] einzutragen. *Um größere oder nicht zusammenhängende Gebiete anzugeben, können mehrere Permalinks eingefügt werden. Du kannst Area-Manager für mehr als ein Gebiet sein. ==Bleibe als Area Manager aktiv== Wenn ein AM 90 Tage lang nicht editiert hat, geht Waze davon aus, dass der Editor nicht mehr aktiv ist. Das AM-Gebiet wird dann ohne Vorankündigung automatisch entzogen. <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 09cff7fd7bd024fe25dcc7235ce8034388338d41 0 73 12125 11909 2021-10-03T22:24:49Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Die Straßenkarten= Die Waze Basis-Karte (Base Map) wurde in vielen Ländern, durch den Import von öffentlich verfügbaren Straßendaten in das System generiert. Diese Daten sind ziemlich genau in der Geometrie, sie können aber etwas Bearbeitung gebrauchen. Außerdem nicht enthalten sind: Zulässige Fahrtrichtungen, Abbiegeregeln, Unterscheidung zwischen befahrbaren und nicht befahrbaren Straßen, wie Eisenbahnen und Fußwege. In den importierten Karten wird auch nicht unterschieden zwischen Brücke oder Kreuzung. Standardmässig ist alles mit einer Kreuzung verbunden und braucht daher definitiv Bearbeitung und Pflege. Hier kommen zwei wichtige Aspekte ins Spiel: #Der Karteneditor für die Benutzer, welche die Karten ihrer Stadtteile, Städte oder anderer Orte bearbeiten, mit denen sie vertraut sind. #Das Sammeln von GPS-Daten der App-Benutzer um die Karte automatisiert zu modifizieren, Fahrtrichtungen und Abbiegungen an Kreuzungen zu ermitteln. In einigen Ländern sind keine Basis-Daten verfügbar für die Straßenkarte, die Karten in diesen Ländern müssen von Grund auf neu aufgebaut werden. Sie werden durch die Benutzer im Karteneditor erstellt. Dabei werden aufgezeichnete Straßen der Waze-App und im Karteneditor neugezeichnete Straßen verwendet. Zur Hilfe stehen im Karteneditor gesammelte GPS-Punkte und vielerorts Luftaufnahmen zur Verfügung. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Karteneditor= *Der Standard-Editor für Waze heißt "Waze Map-Editor" oder kurz "WME". *Der WME wurde mit dem internen Codenamen "Papyrus" versehen. *Wenn Du an der Karte arbeitest, bitte [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] beachten. *Mit dem Karteneditor kannst Du alles in einer vordefinierten Gegend bearbeiten. Diese richtet sich nach den [[Rechte_zum_Bearbeiten_der_Karte#Rechte_basierend_auf_Fahrten|Rechten]], die Du bei Deiner Fahrt erwirbst oder der Funktion, die Dir zugesprochen wurde. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Simulation== Du kannst den Karteneditor auch einfach ausprobieren, dafür wurde eine Simulation geschaffen. Deine Änderungen werden nicht übernommen und auch nicht auf der Karte erscheinen. Probiers und schau Dir auch das Video an! Wenn Du den Karteneditor das erste Mal startest, siehst Du folgendes: [[Image:Playmode1.png|700px|alternativtext=]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Im Karteneditor anmelden== *Unterstützt wird offiziell der Chrome Browser. Der Karteneditor läuft aber auch mit Firefox oder Safari. '''Die Anmeldung:''' *Anmeldung im Waze-Konto mit dem Benutzernamen auf der Waze-Homepage, der Link zur Anmeldung befindet sich oben rechts auf der Seite https://www.waze.com/de/ *Auswahl des Links "Echtzeit-Karte" in der Haupt-Navigationsleiste *Auswahl des Links "Karteneditor" in der Suchleiste *Du kannst Dich auch direkt im Karteneditor anmelden mit Benutzername und Passwort: https://www.waze.com/de/editor/ *Du kannst den Link auch als Lesezeichen ablegen *Auf der Seite [[WME Tipps und Tricks]] gibt es Informationen dazu. Wenn Du Dich korrekt angemeldet hast, siehst Du folgendes: [[Image:Login1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Start-Position des Karteneditors== Um den Karteneditor an einer bestimmten Stelle zu starten: #Wähle den gewünschten Kartenausschnitt aus. #Klick auf Permalink #Kopiere die URL in der Adressleiste deines Browsers in die Lesezeichen. *So kannst Du ein Gebiet deiner Wahl als Startpunkt des Karteneditors bestimmen. Immer wenn Du den Karteneditor über das Lesezeichen öffnest, wird er Dich genau an diese Stelle bringen. *Der Karteneditor öffnet sich in der Regel an der Stelle, wo Du als letztes gearbeitet hast. Es sei denn Du löschst den Cache deines Browsers. Dann ist der Startpunkt London. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Auswählen der Sprache== Die Sprachauswahl des Karteneditors befindet sich in der oberen, rechten Ecke der Haupt-Navigationsleiste [[File:Sprachauswahl.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Oberfläche und Steuerelemente= ==Aussehen des Karteneditors== Es gibt drei Hauptelemente im Waze Map-Editor: #Die Werkzeugleiste #Die Reiter #Der Anzeigebereich der Karte [[File:Anzeige4.png|700px]] Zuoberst ist die Werkzeugleiste mit einem Suchfeld und Buttons für: Hinzufügen, Speichern, Rückgängig, Wiederholen und Löschen.<br> Auf der linken Seite befinden sich die Reiter. Wenn kein Segment ausgewählt ist, zeigen die Reiter: *'''Ich''' Deinen Benutzernamen, das Total Deiner Punkte, Deine Rechte und einen Link zum Map Editing Video. *'''Fahrten''' Wo Du mit Waze gefahren bist. *'''Gebiete''' Wo Du überall die Karte bearbeiten darfst. Wenn ein Segment ausgewählt ist, zeigen die Reiter: *'''Eigenschaften''' Alle Eigenschaften an, die Du bearbeiten kannst. Straßentyp, Richtung, Level, Mautstraße oder Straßen sperren (Lock) *'''Bearbeiten''' zeigt alle anderen Eigenschaften, wie: Land, Stadt, Straße oder Alternative Straßennamen. *'''Gesamte Straße auswählen''' erlaubt das Auswählen eines gesamten Straßenzugs. *'''Hausnummern bearbeiten''' erlaubt das Bearbeiten von Hausnummern für ein ausgewähltes Segment. Dies ist nur für ein einziges Segment möglich. Oben links unterhalb der Werkzeugleiste befindet sich: *Die Anzeige des aktuellen Orts. Auf der rechten Seite unterhalb der Werkzeugleiste: *Der Lade-Indikator (Karte lädt, Speichern etc.) und die Ebenen-Auswahl. Am unteren Rand des Hauptfensters befindet sich: *In der linken Ecke die Skala des Zoom-Stufen. *In der rechten Ecke die Permalink-Schaltfläche und die Anzeige des Längen- und Breitengrads der aktuellen Maus-Zeiger-Position. Auf der linken Seite unterhalb der Reiter befindet sich eine Schaltfläche mit Links zum Wiki, Forum, Status-Seite und zu den Tastaturkürzeln des Karteneditors.<br> [[File:EditorLinks.png]] Der Anzeigebereich der Karte, welcher die größte Fläche einnimmt, bietet die Möglichkeit zur Anzeige der Luftaufnahmen, Städte, Straßen, Kreuzungen, Orientierungspunkte, Blitzer, GPS-Punkte, Kartenfehler und der Gebiete, die man bearbeiten darf. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Werkzeugleiste== [[Image:WME-Werkzeugleiste.png|700px]] ===Das Suchfeld=== Im Suchfeld kann man Adressen, Städte, Staaten, Länder, Orientierungspunkte oder eine Kombination derer eingeben. Nach Betätigen der Eingabe-Taste oder klicken auf den Such-Button, wird entweder eine Auswahl angezeigt oder nur der gesuchte Ort. Beispiel: Suche nach "Blumenstraße, München" Wird dich an die gewünschte Adresse bringen und setzt einen Marker auf die Karte. [[Image:Suchfeld1.png|700px]] Eine Suche nach "Blumenstraße", zeigt einige Ergebnisse an. [[Image:Suchfeld2.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Hinzufügen=== [[Image:Button-hinzufügen.png|left]] Tastaturkürzel: '''i''', '''o''', '''u''', '''g''' oder '''p''' Der Hinzufügen-Button muss nur mit der Maus berührt werden, und es öffnet sich ein Menü mit den Aktionen. Von hier aus kannst Du Straßen, Kreisverkehre oder Orientierungspunkte etc. hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Speichern=== [[Image:Speichern1.png |left]] [[Image:Speichern2.png]] [[Image:Speichern3.png]] Tatstaturkürzel: '''Ctrl+s''' <br> Der Speichern-Button speichert alle aktuellen Bearbeitungsschritte. Der Button besitzt einen Zähler. 0-9 Bearbeitungsschritte werden in schwarzen Ziffern angezeigt und ab 10 Bearbeitungsschritten erscheinen die Ziffern rot. Wenn es beim Speichern einen Fehler gibt, erscheint ein Fenster mit einer Fehlermeldung, die das Problem normalerweise beschreibt. Der Map-Editor versucht die Stelle auf der Karte anzuzeigen, wo der Fehler liegt und zeigt den Fehler in Form eines hellen Kreises an. Sobald der Speichern-Button angeklickt wird, ist es nicht mehr möglich etwas rückgängig zu machen! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Rückgängig=== [[Image:Button-rueckgaengig.png|left]] Tastaturkürzel: '''Ctrl+Z''' Der Rückgängig-Button macht Schrittweise die Bearbeitungsschritte rückgängig, die '''noch nicht gespeichert''' wurden. <span style="color:red;">Wurde bereits gespeichert, ist es nicht mehr möglich etwas rückgängig zu machen, das man zuvor bearbeitet hat!</span> Ein Bearbeitungsschritt kann das Löschen einer Kreuzung sein, die Benennung einer Straße oder sonstigem. Wenn Du aber 10 Segmente auswählst und gleichzeitig bearbeitest um sie z.B. von "Unknown" auf 2spurig umzustellen, dann gilt dies als ein Bearbeitungsschritt, wenn Du den Rückgängig-Button drückst. Alle 10 Segmente werden dann rückgängig gemacht! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Wiederholen=== [[Image:Button-wiederholen.png|left]] Tastaturkürzel: '''Ctrl+Shift+Z''' Der Wiederholen-Button wiederholt alles, was der Rückgängig-Button zuvor rückgängig gemacht hat. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Löschen=== [[Image:Button-loeschen.png|left]] Tastaturkürzel: '''Delete (Del)''' Der Löschen-Button löscht alles was ausgewählt ist. Sind mehrere Segmente ausgewählt, muss man dies auf einem Popup bestätigen und danach kann gespeichert werden. Das einzige, was im Moment in Mehrfach-Auswahl gelöscht werden kann sind Straßen-Segmente. Der Rückgängig-Button kann auch bereits zur Löschung ausgewählte Objekte wiederherstellen, '''solange nicht gespeichert''' wurde nach dem Löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Reiter== [[File:Hallo.png]] Zuoberst grüßt man dich mit deinem Benutzernamen und zeigt dir das Total deiner Punkte an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Ich=== [[Image:Wazer-rechte.png]] Der Ich-Reiter zeigt einen Wazer mit gelbem Bauhelm, und die entsprechenden Rechte. Sie werden in orangfarbenen Pylonen dargestellt. Weiteres dazu [[Rechte zum Bearbeiten der Karte|hier]]. Darunter wird angezeigt, welche Rechte Du besitzt und das Total Deiner Punkte. Unterhalb der Benutzerinformationen befindet sich diese Schaltfläche: [[File:Benutzer Video.png]] Sie öffnet ein Interface, das 7 Videos über Waze auf Youtube enthält. Diese Videos sind auf Englisch und heißen: #Einführung #Bevor Du beginnst #Erste Schritte #Grundbegriffe #Grundlagen #Kartenfehler #Beispiele Diese animierte Anleitung ist ein guter Weg, um einen Überblick über das System und einige der Prozesse zu bekommen. Diese Videos sind nur eine Einführung. In den Dokumentationen und den [[Main_Page|Waze-Wikis]] sind die meisten Details über den Karteneditor zu finden. Auch wenn es um Richtlinien für Standards und länderspezifische Eigenheiten geht, sind diese unerlässlich. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Fahrten=== Unter "Fahrten" siehst Du die Strecken, die Du mit Waze gefahren bist. Wenn Du einen Eintrag auswählst, zoomt die Karte dahin und zeigt die Strecke innerhalb der Karte an. Oben auf der Karte wird ein Fenster angezeigt, das Dir zeigt, welche Strecke Du gefahren bist. Routen die länger als 20 Meilen/32 Kilometer sind, zeigt der Editor nicht innerhalb der Karte an. Du kannst dann anhand der gefahrenen Strecke eine Straße auf die Karte zeichnen, wenn Du "Straße erstellen" anklickst. Die Straßen, die Du erstellen kannst, zeigt der Streckenverlauf rot an. Erstelle keine Segmente über bereits bestehende Straßen. Schau Dir zuerst die Karte an! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Gebiete=== Diese Liste zeigt definierte Gebiete an, in denen Du arbeiten kannst. Entweder die Gebiete, die Du befahren hast oder die Gebiete in denen Du Area- oder Country-Manager bist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Segmente== [[File:Reiteranzeige.png|right]] [[File:Ausgewaehlt editmodus.png|right]] '''Einzelnes Segment ausgewählt:'''<br> Im oberen Teil werden der Name des Segments und die "Alternativen Straßennamen" angezeigt. Darunter der Bearbeiten-Button. Im unteren Teil wird Straßentyp, Richtung, Ebene und Stufe der Sperre angezeigt. '''Bei Mehrfach-Auswahl:'''<br> Der obere Bereich zeigt an, wie viele Segmente ausgewählt sind. Das Beispiel rechts zeigt, wie die Situation aussieht, wenn 2 Segmente ausgewählt sind im "Bearbeiten-Modus". '''Eigenschaften bearbeiten:'''<br> Wenn Du auf Bearbeiten klickst oder das Tastaturkürzel '''"e"''' drückst, wechselt die Ansicht in den Bearbeiten-Modus und zeigt alle wichtigen Informationen an. Es ermöglicht Dir alle Eigenschaften wie: Landes-, Stadt- und Straßennamen zu ändern. Das Feld für Bundesländer/Kantone resp. Staaten ist im Moment noch den USA vorbehalten. Auch alternative Straßennamen kannst Du bearbeiten. Dies ist dann interessant, wenn die Straße einen lokalen Namen besitzt, der nicht im Hauptfeld des Segments Platz hat, oder nicht offiziell gebräuchlich ist. Beispiel: Die A1 in Österreich hat im alternativen Namen die Bezeichnung "West Autobahn" Oder das Beispiel, das im Screenshot zu sehen ist.<br> '''Das Stadt-Feld des alternativen Namens muss den selben Namen, wie das Stadt-Feld des Segments besitzen.''' <br style="clear: both" /> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Orientierungspunkte== {| border="0" cellpadding="2" style="background:none;" |- style="vertical-align:top;" |Wenn Du eine Orientierungspunkt auswählst, kannst Du ihn benennen, einen Orientierungspunkt-Typ vergeben und den Orientierungspunkt mit einer Sperre versehen. Die Sperre hindert Editoren mit niedrigeren Stufen (Rechte) den Orientierungspunkt zu verändern: | |Darunter befinden sich die Adressdetails. ''Klick'' auf '''Bearbeiten''' und ändere die Details, ''klick'' auf '''Übernehmen''', wenn Du alles eingegeben hast: |- style="vertical-align:top;" |[[File:Orientierungspunktausgewaehlt.png]] | |[[File:Orientierungspunktausgewaehltadressdetails.png]] Wird eine korrekte Adresse eingegeben, ermöglichen wir damit Waze, die interne Suche für die Orientierungspunkte zu verwenden und nicht externe Anbieter. |} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Anzeigebereich der Karte= Alle ausgewählten Ebenen sind im Anzeigebereich der Karte zu sehen. Der Anzeigebereich der Karte nimmt den Hauptteil des Browser-Fensters ein. Jedes Objekt, das angezeigt wird ist auswählbar und kann bearbeitet werden. Dies hängt von den Rechten ab, die Du im ausgewählten Kartenausschnitt besitzt. Wähle eine Straße aus und verändere ihre Geometrie. Wähle einen Orientierungspunkt aus und gebe ihm einen Namen. Füge eine Straße hinzu, wo eine sein sollte oder lösche Straßen, die nicht mehr zu sehen sein sollen. Es gibt sieben Hauptbestandteile in den Ecken des Anzeigebereichs auf der Karte: #Die Infoleiste #Die Zoom-Steuerung inkl. Streetview #Die Schaltfläche für den Chat #Die Ebenen-Auswahl #Die Permalink-Schaltfläche #Die Anzeige des Längen- und Breitengrades #Die Zoom-Skala </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Info Leiste== [[File:Infoleiste.png|700px]] Unter dem Suchfeld befindet sich die Info-Leiste. *Links die Stadt und das Land des aktuellen Kartenausschnitts. *Rechts befindet sich eine Box, die nur erscheint, wenn etwas geladen wird. Karte lädt, Speichern, Straßen laden etc. Daneben die Ebenen-Auswahl. Probleme beim Speichern können hauptsächlich beim Verbinden an Kreuzungen und Geometrieänderungen entstehen. Deshalb arbeite sorgfältig, und Du ersparst dir Mehraufwand. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Zoom-Steuerung== [[Image:Zoomregler.png|left]] Tastaturkürzel: '''Shift+UpArrow''', Tastaturkürzel: '''Shift+DownArrow''' In der oberen linken Ecke befindet sich die Zoom-Skala, sie besitzt 10 Stufen. Die Steuerung der Skala + und - kann benutzt werden, um die Karte zu vergrößern oder zu verkleinern. Dies funktioniert auch, wenn der Regler verschoben wird, oder am einfachsten, wenn man am Mausrad dreht. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Streetview== [[Image:Streetview.png]] Direkt unter der Zoom-Steuerung befindet sich der Streetview. Ziehe die blaue Linse auf die Straße, die Du im Streetview anschauen möchtest. Der Streeview ist nicht überall vorhanden, er hängt davon ab, was uns Google zur Verfügung stellt. [[Image:Streetview-nicht-vorhanden.png|left]] Wo kein Streetview verfügbar ist, bleibt die Linse beim Ziehen über der Karte rot. <br style="clear: both" /> [[Image:Streetview-vorhanden.png|left]] Wo der Streetview verfügbar ist, färbt sich die Linse beim Ziehen über der Karte blau, Du kannst die Linse loslassen und die Straße im Streetview anschauen. <br style="clear: both" /> Wenn Du die Linse losgelassen hast, enthält sie einen Pfeil, der in die Richtung des Streetviews zeigt. [[Image:Wme streetview directional arrow.gif]] Während des Streetviews sind alle anderen Operationen möglich (Segment-Eigenschaften, Kartenfehler und Aktualisierungsanfragen, Hausnummern, zeitliche Beschränkungen etc.) Die Rechte Seite des Fensters enthält den Streetview. Du kannst die Ansicht in alle Richtungen verschieben mit der Maus, oder mit der Steuerung oben links im Streetview-Fenster. Zoomen kannst Du über den Regler oder mit dem Mausrad. Um die Position der Ansicht zu verschieben, kannst Du auf die Pfeile unterhalb der Bildmitte klicken oder Dich per Mausklick fortbewegen. Du kannst auch die Linse auf der Karte verschieben, mit dem kleinen weißen Punkt darunter. [[Image:Streetview-situation.png|700px]] Wenn Du zu viel auf einmal aktivierst, wirst Du feststellen, dass der bearbeitbare Bereich auf der Karte immer kleiner wird. Z.B. eine Aktualisierungsanfrage mit dem Fenster für Kommentare. Denke an die Tastaturkürzel, denn der Zoom-Regler der Karte ist dann verdeckt und somit kannst Du nur noch mit den Tastaturkürzeln Zoomen. Um den Streetview zu beenden, klicke auf das X in der oberen, rechten Ecke des Streetview-Fensters. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Der Editor-Chat== Wird demnächst erstellt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ebenen-Auswahl== Auf der rechten Seite der Karte findest Du dieses Symbol: [[Image:Layers-Auswahl.png]] Wenn Du mit der Maus darüber fährst, zeigt es Dir an, welche Ebenen aktuell ausgewählt sind. Die Ebenen mit den vier Punkten vor dem Namen, kannst Du in der Auswahl beliebig anordnen. [[WME_Schnellstart-Anleitung#Tastaturk.C3.BCrzel|'''Tastaturkürzel''']]. [[File:Ebenen.png]] Hier ein paar Informationen dazu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Die Luftaufnahmen=== [[Image:Aerial_skinny.png|260px]] Tastaturkürzel: '''Shift+b''' Waze benutzt Luftaufnahmen von Google (oder VirtualEarth). </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Städte=== [[Image:cities_skinny.png|260px]] Tastaturkürzel: '''Shift+c''' Diese Ebene zeigt die Grenzen der Städte verschiedenfarbig an in Form von Polygonen. Je nachdem, wie die Segmente benannt wurden. Dies ist hilfreich, um falsch benannte Segmente zu identifizieren. Manchmal können die Grenzen überlappen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Straßen=== [[Image:Road_segments_skinny.png|260px]] Tastaturkürzel: '''Shift+r''' In der Ebene sind die Straßen, Gassen, Autobahnen etc., aus denen sich die fahrbare Karte des Systems in Waze zusammensetzt. Je nach Zoom-Stufe sind einige Straßen nicht sichtbar, damit die Karte nicht zu unübersichtlich dargestellt wird. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===GPS-Punkte=== [[Image:Gps_tracks_straight_skinny.png|260px]] Tastaturkürzel: '''Shift+g''' Diese Ebene zeigt die GPS-Punkte der Benutzer an, die mit der Waze-App herumgefahren sind. Waze zeichnet die GPS-Koordinaten der Fahrer auf und wandelt sie in farbige Pfeile um, diese sind dann in der Karte sichtbar. Diese Ebene ist sehr hilfreich, um Straßen auf der Karte an richtiger Stelle zu platzieren, wenn z.B. keine Luftbilder vorhanden sind. Die Pfeile haben unterschiedliche Farben in jeder Fahrtrichtung. Das macht es einfacher, fehlerhafte GPS-Spuren zu lokalisieren oder Straßen auf der Karte zu finden, die nicht dem tatsächlichen Straßenverlauf folgen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Area-Manager=== Zeigt die Area-Manager im ausgewählten Ausschnitt an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Orientierungspunkte=== [[Image:Landmarks_skinny.png|260px]] Tastaturkürzel: '''Shift+l''' Orientierungspunkte sind auch unter Landmarks oder POI's (Points of Interest) bekannt. Diese können für nahezu alles verwendet werden: Tankstellen, Parks, Flüsse. Friedhöfe etc. Mehr Informationen zu den Orientierungspunkten findest Du [[Erstellen und bearbeiten von Landmarks|hier]]. </noinclude></noinclude> </noinclude> </noinclude> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Kartenfehler=== [[Image:Problem_pin_open-low.gif|left]][[Image:Problem_pin_open-med.gif]] [[Image:Problem_pin_open-high.gif]] Tastaturkürzel: '''Shift+p''' <br> Der Waze-Server analysiert laufend die GPS-Daten, um Fehler zu erkennen. Diese werden dann über die Ebene Kartenfehler sichtbar. Sie sollen den Benutzer, der die Karte bearbeitet darauf hinweisen, dass die Karte Fehler aufweist, die es zu bearbeiten gilt. Typische Kartenfehler sind: Fehlende Straßen, falsche Abbiegungen, falsche Einbahnstraßen oder fehlende Verbindungen zwischen Segmenten. Für Informationen, lies [[WME Map Problems]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Aktualisierungsanfragen=== [[Image:Request_pin_open-low.gif|left]][[Image:Request_pin_open-med.gif]] [[Image:Request_pin_open-high.gif]] Tastaturkürzel: '''Shift+u''' <br> Die Aktualisierungsanfragen werden von den Benutzern der Waze-App während der Fahrt oder auf der "Echtzeit-Karte" gemeldet. *Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei gefahren ist, zeigt die Ebene im Karteneditor hellgrün an. *Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei während der Navigation gefahren ist, zeigt die Ebene im Karteneditor lila an mit den Abbiege-Anweisungen, die der Benutzer dabei erhalten hat. *Für Informationen, lies [[WME Update Requests]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Meine Gebiete=== [[Image:Editable_area_skinny.png|260px]] Tastaturkürzel: '''Shift+e''' Wo Du die Karte bearbeiten kannst, hängt davon ab, wo Du mit der Waze-App gefahren bist. Die Rechte sind im Umkreis von 1 Meile bzw. 1,6 Kilometer um die befahrene Strecke vorhanden. Die Gebiete die Du bearbeiten kannst, zeigen sich im Karteneditor wie folgt: *Hell hinterlegt sind Gebiete, die Du mit Waze befahren hast. *Die farbigen Gebiete sind die, in denen Du Area-Manager bist. *Dunkle Gebiete kannst Du nicht bearbeiten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Permalink-Schaltfläche== [[Image:Permalink-neu.png]] Außerhalb der Karte unten rechts befindet sich die Permalink-Schaltfläche. Der Permalink ändert immer dann, wenn die Karte verschoben wird, Objekte ausgewählt oder deselektiert werden. Man beachte: Der Permalink wird nicht jedesmal automatisch neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn man eine Browser-Sitzung wiederherstellt inkl. Editor, wird der Browser die letzte Kartenposition des Permalinks anzeigen, den man zuvor generiert hat. Wenn man Permalink anklickt, speichert dieser alle Informationen für den ausgewählten Kartenausschnitt. Man kann ihn anklicken, um die Karte zu aktualisieren, mit einem Rechtsklick kopieren, mit anderen Benutzern im Forum teilen oder als Lesezeichen ablegen. Vor allem bei Fragen zur Karte wird der Permalink im Forum oft gebraucht. Denn er speichert auch ausgewählte Straßen, Kreuzungen und Landmarks, so zeigt er anderen Benutzern schnell, was gemeint ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Anzeige des Längen- und Breitengrades== [[Image:Koordinaten.png]] In der unteren rechten Ecke befindet sich die Anzeige des Längen- und Breitengrades. Sie zeigt den aktuellen Ort, wo der Mauszeiger gerade hinzeigt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Zoom-Skala== {| style="float:left; background: transparent;" width="400" |[[Image:Zoom-Skala.png|left]] |- |Unten rechts befindet sich die Anzeige der Zoom-Stufe. Die Werte in der Skala rechts entsprechen auch der [[#Zoom-Steuerung | Zoomstufe]], die Du in der URL des Browsers siehst (zoom=5). Änderst Du die Zoomstufe darin, verändert sich auch die Ansicht. |} {| style="float:right;" |[[Image:Stufenscala.png]] |} {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karteneditor Steuerung= *Bewege die Karte, indem Du sie mit der Maus umherziehst. *Mit den Pfeiltasten kannst Du die Karte in alle vier Richtungen verschieben. *Es gibt vier Möglichkeiten die Karte zu zoomen: #Über die Zoom-Steuerung am linken oberen Rand der Karte. Regler hoch oder runterziehen mit der Maus oder klicke auf die + oder - Buttons. #Ein Doppelklick auf der Karte zoomt die Karte um eine Stufe rein und zentriert den Ausschnitt an den Ort, wohin man geklickt hat. #Am Mausrad drehen. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. Auf dem Mac mit einem Trackpad oder ähnlichem, nach links und rechts ziehen bewirkt das selbe. #Die ''Shift'' Taste drücken und ein Rechteck auf der Karte Zeichnen. Die Karte zoomt den ausgewählten Auschnitt ein: [[Image:Shift_zoom.png|500px|center]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =WME Schnell-Start Anleitung= Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Um die besten Techniken zu kennen und anzuwenden, braucht ein bisschen Zeit. Aber es kann auch Spaß machen mit wachsender Erfahrung. Man kann Stolz sein darauf, die Anwendung mit ein paar einfachen Bearbeitungsschritten für alle Endbenutzer zu verbessern. Die Links später in dieser Anleitung sind sehr wichtig, um alles zu erlernen was es braucht. Für die einfache Bearbeitung gibt es hier die [[WME Schnellstart-Anleitung]] um sich schnell zurecht zu finden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Permalink= :[[Image:wme permalink highlight.jpg]] *Im Karteneditor ist der [[Glossar#Permalink|Permalink]] eine URL, die Dich direkt an einen spezifischen Punkt auf der Karte bringt. Er speichert Längen- und Breitengrad, Zoom Stufe und alle Sichtbaren Objekte die während der Bearbeitung aktiv sind auf der Karte (ausgewählt in den Ebenen). Um genau auf ein Problem hinzuweisen sollte das betreffende Objekt ausgewählt sein, dies wird nämlich auch gespeichert. *Nach dem Klick auf Permalink unten rechts im Karteneditor, findest Du die Adresse zum Link in der Adresszeile des Browsers. Diese kann kopiert und in Foren-Beiträgen oder Lesezeichen eingefügt werden. Dies funktioniert auch wenn Du Permalink mit der rechten Maustaste auswählt und die Adresse direkt kopierst. *Hinweis: Der Permalink wird nicht jedesmal neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn Du eine Browser Sitzung wiederherstellst inkl. Editor, wird der Browser die letzte Karten-Position des Permalinks anzeigen, den Du zuvor generiert hast. *Falls die Straßen nicht mit den Luftaufnahmen übereinstimmen oder eine ungewöhnliche Position aufweisen, kannst Du mit dem Permalink die Seite aktualisieren, was das Problem in der Regel löst. *Was andere Editoren im Permalink sehen können, hängt von den Rechten ab, die sie besitzen. Ein Editor kann Aktualisierungsanfragen (Update Requests) oder Kartenfehler (Map Problems) nur in seinem bearbeitbaren Gebiet sehen. Also die lokalen Editoren, Area-Manager oder Country-Manager der betreffenden Gebiete oder Länder. Wenn Du ein breiteres Publikum betreffend eines Problems erreichen willst, musst Du ein Bildschirmfoto posten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Permalink in der Echtzeitkarte= Willst Du einen Permalink in der Echtzeitkarte generieren, musst Du auf die Permalink-Schaltfläche in der unteren, rechten Ecke der Karte klicken. Routen werden dabei auch gespeichert. *[[Image:PermalinkLiveMap.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tastaturkürzel= Der Einfachheit halber sind alle Kürzel im [[WME_Schnellstart-Anleitung#Tatstaturk.C3.BCrzel|WME Schnellstart-Anleitung]] an einem Ort zusammengefasst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karten Aktualisierung= Alles was bearbeitet wurde mit dem Karteneditor, wird früher oder später auf der Live Map und in der Waze-App zu sehen sein. Das Ziel von Waze ist es, alle Daten innerhalb von 24 Stunden zu aktualisieren. Dies kann auch mal länger dauern, schau Dir deshalb auch die Seite [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] an. *Die Aktualisierungen und sonstige Ereignisse, werden auch auf der [http://status.waze.com/ Status-Seite] von Waze publiziert. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Einsatz von externen Quellen (wie Google Imagery)= Die Verwendung von beliebigen externen, urheberrechtlich geschützten Informationsquellen, um Informationen in die Datenbank oder die Waze-Karten einzupflegen, ist nicht erlaubt. Externe urheberrechtlich geschützte Informationsquellen beinhaltet alle Online- oder gedruckten Karteninformationen, die nicht von Waze durch die Schnittstelle des Karteneditors bereitgestellt werden. Mit der Akquisition von Waze durch Google, Inc., wurde der Karteneditor von Waze mit Luftaufnahmen von Google und dem Streetview aktualisiert. Diese gelten als interne Quellen und dürfen daher verwendet werden, um Karteninformationen zur Waze-Karte hinzuzufügen. Googles Nutzungsbedingungen binden die Nutzung ihrer Karteninformationen an spezifische Bedingungen und Waze besitzt nur die ordnungsgemäße Lizenz, das was im Karteneditor zu sehen ist auch zu nutzen, aber sonst nichts anderes von Google. Die Verwendung von externen, urheberrechtlich geschützten Quellen gefährden die Karten und Waze wird dadurch gezwungen, alle Änderungen zu löschen und den Urzustand der Karte wieder herzustellen. Dies betrifft alle Änderung des betreffenden Benutzers auf der ganzen Karte! Wenn Du Karten in der Form erstellst, sieht sich Waze leider gezwungen, Deine ganze Arbeit von der Karte zu löschen. So ist es bereits in Chile und anderen Südamerikanischen Ländern passiert aufgrund der Lizenzprobleme. (kein Fehler seitens Waze!) Du darfst gerne mit lokalen Anbietern oder Behörden kommunizieren um allf. Luftaufnahmen oder Informationen zu erhalten, die verwendet werden dürfen. Du musst allerdings dabei klar erwähnen, dass Du nicht für Waze arbeitest oder in Auftrag von Waze handelst. Aber als interessierter Bürger kannst Du natürlich mit den lokalen Behörden sprechen, um die Vorteile für die Allgemeinheit zu erklären, z.B Luftaufnahmen als öffentliches Gut frei zur Verfügung zu stellen. Bei Fragen oder wenn Du nicht sicher bist, kommuniziere unbedingt mit dem Waze-Support. Beachte, dass externe Urheberrechtsinformationen keine Informationsquellen beinhalten, die von Waze durch die internen Werkzeuge des Karteneditors oder der Waze-App zur Verfügung gestellt werden. Auch alle Informationen, die selbstständig von einem Benutzer entwickelt wurden und physisch an einer Stelle abrufbar sind, werden akzeptiert, um damit die Karte zu bearbeiten, solange es nicht urheberrechtlich geschützt zur Verfügung gestellt wurde. Du darfst mit dem Support reden, wenn Du eine Quelle benutzen möchtest und nicht sicher bist, ob Du sie auch verwenden darfst. Waze wird die Quelle prüfen und Dir mitteilen, ob Du sie verwenden darfst oder nicht. Wenn nicht klar ist, ob eine Verwendung Legal ist, gelten die nachfolgenden Verbote. '''Folgendes ist Verboten:''' *Nachschauen ob der Straßenname korrekt ist. *Straßennamen von anderen Karten abtippen. *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren (manuell). *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren mit einem Skript. '''Es ist sehr einfach:''' *Verwende den Karteneditor mit den Möglichkeiten, die innerhalb Waze angeboten werden. *Vermeide alles andere, sofern nicht geprüft und bestätigt von Waze. Darum zeigt Waze im Karteneditor nur die Streetview Bilder ohne zusätzliche Daten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] af6f4e58c5aa95a5870a88b283113366eee15ea7 12127 12125 2021-10-03T22:43:06Z Popel22 24 /* Die Straßenkarten */ wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] =Die Strassenkarten= Die Waze Basis-Karte (Base Map) wurde in vielen Ländern, durch den Import von öffentlich verfügbaren Straßendaten in das System generiert. Diese Daten sind ziemlich genau in der Geometrie, sie können aber etwas Bearbeitung gebrauchen. Außerdem nicht enthalten sind: Zulässige Fahrtrichtungen, Abbiegeregeln, Unterscheidung zwischen befahrbaren und nicht befahrbaren Strassen, wie Eisenbahnen und Fusswege. In den importierten Karten wird auch nicht unterschieden zwischen Brücke oder Kreuzung. Standardmässig ist alles mit einer Kreuzung verbunden und braucht daher definitiv Bearbeitung und Pflege In einigen Ländern sind keine Basis-Daten verfügbar für die Straßenkarte, die Karten in diesen Ländern müssen von Grund auf neu aufgebaut werden. Sie werden durch die Benutzer im Karteneditor erstellt. Dabei werden aufgezeichnete Straßen der Waze-App und im Karteneditor neugezeichnete Straßen verwendet. Zur Hilfe stehen im Karteneditor gesammelte GPS-Punkte und vielerorts Luftaufnahmen zur Verfügung. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Karteneditor= *Der Standard-Editor für Waze heißt "Waze Map-Editor" oder kurz "WME". *Wenn Du an der Karte arbeitest, bitte [[Die beste Vorgehensweise beim Bearbeiten der Karte | Die beste Vorgehensweise]] beachten. *Mit dem Karteneditor kannst Du alles in einer vordefinierten Gegend bearbeiten. Diese richtet sich nach den [[Rechte_zum_Bearbeiten_der_Karte#Rechte_basierend_auf_Fahrten|Rechten]], die Du bei Deiner Fahrt erwirbst oder der Funktion, die Dir zugesprochen wurde.<br /> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Simulation== Du kannst den Karteneditor auch einfach ausprobieren, dafür wurde eine Simulation geschaffen. Deine Änderungen werden nicht übernommen und auch nicht auf der Karte erscheinen. Probiers und schau Dir auch das Video an! Wenn Du den Karteneditor das erste Mal startest, siehst Du folgendes: [[Image:Playmode1.png|700px|alternativtext=]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Im Karteneditor anmelden== *Unterstützt wird offiziell der Chrome Browser. Der Karteneditor läuft aber auch mit Firefox oder Safari. '''Die Anmeldung:''' *Anmeldung im Waze-Konto mit dem Benutzernamen auf der Waze-Homepage, der Link zur Anmeldung befindet sich oben rechts auf der Seite https://www.waze.com/de/ *Auswahl des Links "Echtzeit-Karte" in der Haupt-Navigationsleiste *Auswahl des Links "Karteneditor" in der Suchleiste *Du kannst Dich auch direkt im Karteneditor anmelden mit Benutzername und Passwort: https://www.waze.com/de/editor/ *Du kannst den Link auch als Lesezeichen ablegen *Auf der Seite [[WME Tipps und Tricks]] gibt es Informationen dazu. Wenn Du Dich korrekt angemeldet hast, siehst Du folgendes: [[Image:Login1.png|700px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Start-Position des Karteneditors== Um den Karteneditor an einer bestimmten Stelle zu starten: #Wähle den gewünschten Kartenausschnitt aus. #Klick auf Permalink #Kopiere die URL in der Adressleiste deines Browsers in die Lesezeichen. *So kannst Du ein Gebiet deiner Wahl als Startpunkt des Karteneditors bestimmen. Immer wenn Du den Karteneditor über das Lesezeichen öffnest, wird er Dich genau an diese Stelle bringen. *Der Karteneditor öffnet sich in der Regel an der Stelle, wo Du als letztes gearbeitet hast. Es sei denn Du löschst den Cache deines Browsers. [[Datei:PL.jpg|links|mini|47x47px]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Auswählen der Sprache== Die Sprachauswahl des Karteneditors befindet sich in der oberen, rechten Ecke der Haupt-Navigationsleiste [[File:Sprachauswahl.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Oberfläche und Steuerelemente= ==Aussehen des Karteneditors== Es gibt drei Hauptelemente im Waze Map-Editor: #Die Werkzeugleiste #Die Reiter #Der Anzeigebereich der Karte [[File:Anzeige4.png|700px]] Zuoberst ist die Werkzeugleiste mit einem Suchfeld und Buttons für: Hinzufügen, Speichern, Rückgängig, Wiederholen und Löschen.<br> Auf der linken Seite befinden sich die Reiter. Wenn kein Segment ausgewählt ist, zeigen die Reiter: *'''Ich''' Deinen Benutzernamen, das Total Deiner Punkte, Deine Rechte und einen Link zum Map Editing Video. *'''Fahrten''' Wo Du mit Waze gefahren bist. *'''Gebiete''' Wo Du überall die Karte bearbeiten darfst. Wenn ein Segment ausgewählt ist, zeigen die Reiter: *'''Eigenschaften''' Alle Eigenschaften an, die Du bearbeiten kannst. Straßentyp, Richtung, Level, Mautstraße oder Straßen sperren (Lock) *'''Bearbeiten''' zeigt alle anderen Eigenschaften, wie: Land, Stadt, Straße oder Alternative Straßennamen. *'''Gesamte Straße auswählen''' erlaubt das Auswählen eines gesamten Straßenzugs. *'''Hausnummern bearbeiten''' erlaubt das Bearbeiten von Hausnummern für ein ausgewähltes Segment. Dies ist nur für ein einziges Segment möglich. Oben links unterhalb der Werkzeugleiste befindet sich: *Die Anzeige des aktuellen Orts. Auf der rechten Seite unterhalb der Werkzeugleiste: *Der Lade-Indikator (Karte lädt, Speichern etc.) und die Ebenen-Auswahl. Am unteren Rand des Hauptfensters befindet sich: *In der linken Ecke die Skala des Zoom-Stufen. *In der rechten Ecke die Permalink-Schaltfläche und die Anzeige des Längen- und Breitengrads der aktuellen Maus-Zeiger-Position. Auf der linken Seite unterhalb der Reiter befindet sich eine Schaltfläche mit Links zum Wiki, Forum, Status-Seite und zu den Tastaturkürzeln des Karteneditors.<br> [[File:EditorLinks.png]] Der Anzeigebereich der Karte, welcher die größte Fläche einnimmt, bietet die Möglichkeit zur Anzeige der Luftaufnahmen, Städte, Straßen, Kreuzungen, Orientierungspunkte, Blitzer, GPS-Punkte, Kartenfehler und der Gebiete, die man bearbeiten darf. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Werkzeugleiste== [[Image:WME-Werkzeugleiste.png|700px]] ===Das Suchfeld=== Im Suchfeld kann man Adressen, Städte, Staaten, Länder, Orientierungspunkte oder eine Kombination derer eingeben. Nach Betätigen der Eingabe-Taste oder klicken auf den Such-Button, wird entweder eine Auswahl angezeigt oder nur der gesuchte Ort. Beispiel: Suche nach "Blumenstraße, München" Wird dich an die gewünschte Adresse bringen und setzt einen Marker auf die Karte. [[Image:Suchfeld1.png|700px]] Eine Suche nach "Blumenstraße", zeigt einige Ergebnisse an. [[Image:Suchfeld2.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Hinzufügen=== [[Image:Button-hinzufügen.png|left]] Tastaturkürzel: '''i''', '''o''', '''u''', '''g''' oder '''p''' Der Hinzufügen-Button muss nur mit der Maus berührt werden, und es öffnet sich ein Menü mit den Aktionen. Von hier aus kannst Du Straßen, Kreisverkehre oder Orientierungspunkte etc. hinzufügen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Speichern=== [[Image:Speichern1.png |left]] [[Image:Speichern2.png]] [[Image:Speichern3.png]] Tatstaturkürzel: '''Ctrl+s''' <br> Der Speichern-Button speichert alle aktuellen Bearbeitungsschritte. Der Button besitzt einen Zähler. 0-9 Bearbeitungsschritte werden in schwarzen Ziffern angezeigt und ab 10 Bearbeitungsschritten erscheinen die Ziffern rot. Wenn es beim Speichern einen Fehler gibt, erscheint ein Fenster mit einer Fehlermeldung, die das Problem normalerweise beschreibt. Der Map-Editor versucht die Stelle auf der Karte anzuzeigen, wo der Fehler liegt und zeigt den Fehler in Form eines hellen Kreises an. Sobald der Speichern-Button angeklickt wird, ist es nicht mehr möglich etwas rückgängig zu machen! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Rückgängig=== [[Image:Button-rueckgaengig.png|left]] Tastaturkürzel: '''Ctrl+Z''' Der Rückgängig-Button macht Schrittweise die Bearbeitungsschritte rückgängig, die '''noch nicht gespeichert''' wurden. <span style="color:red;">Wurde bereits gespeichert, ist es nicht mehr möglich etwas rückgängig zu machen, das man zuvor bearbeitet hat!</span> Ein Bearbeitungsschritt kann das Löschen einer Kreuzung sein, die Benennung einer Straße oder sonstigem. Wenn Du aber 10 Segmente auswählst und gleichzeitig bearbeitest um sie z.B. von "Unknown" auf 2spurig umzustellen, dann gilt dies als ein Bearbeitungsschritt, wenn Du den Rückgängig-Button drückst. Alle 10 Segmente werden dann rückgängig gemacht! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Wiederholen=== [[Image:Button-wiederholen.png|left]] Tastaturkürzel: '''Ctrl+Shift+Z''' Der Wiederholen-Button wiederholt alles, was der Rückgängig-Button zuvor rückgängig gemacht hat. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Löschen=== [[Image:Button-loeschen.png|left]] Tastaturkürzel: '''Delete (Del)''' Der Löschen-Button löscht alles was ausgewählt ist. Sind mehrere Segmente ausgewählt, muss man dies auf einem Popup bestätigen und danach kann gespeichert werden. Das einzige, was im Moment in Mehrfach-Auswahl gelöscht werden kann sind Straßen-Segmente. Der Rückgängig-Button kann auch bereits zur Löschung ausgewählte Objekte wiederherstellen, '''solange nicht gespeichert''' wurde nach dem Löschen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Reiter== [[File:Hallo.png]] Zuoberst grüßt man dich mit deinem Benutzernamen und zeigt dir das Total deiner Punkte an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Ich=== [[Image:Wazer-rechte.png]] Der Ich-Reiter zeigt einen Wazer mit gelbem Bauhelm, und die entsprechenden Rechte. Sie werden in orangfarbenen Pylonen dargestellt. Weiteres dazu [[Rechte zum Bearbeiten der Karte|hier]]. Darunter wird angezeigt, welche Rechte Du besitzt und das Total Deiner Punkte. Unterhalb der Benutzerinformationen befindet sich diese Schaltfläche: [[File:Benutzer Video.png]] Sie öffnet ein Interface, das 7 Videos über Waze auf Youtube enthält. Diese Videos sind auf Englisch und heißen: #Einführung #Bevor Du beginnst #Erste Schritte #Grundbegriffe #Grundlagen #Kartenfehler #Beispiele Diese animierte Anleitung ist ein guter Weg, um einen Überblick über das System und einige der Prozesse zu bekommen. Diese Videos sind nur eine Einführung. In den Dokumentationen und den [[Main_Page|Waze-Wikis]] sind die meisten Details über den Karteneditor zu finden. Auch wenn es um Richtlinien für Standards und länderspezifische Eigenheiten geht, sind diese unerlässlich. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Fahrten=== Unter "Fahrten" siehst Du die Strecken, die Du mit Waze gefahren bist. Wenn Du einen Eintrag auswählst, zoomt die Karte dahin und zeigt die Strecke innerhalb der Karte an. Oben auf der Karte wird ein Fenster angezeigt, das Dir zeigt, welche Strecke Du gefahren bist. Routen die länger als 20 Meilen/32 Kilometer sind, zeigt der Editor nicht innerhalb der Karte an. Du kannst dann anhand der gefahrenen Strecke eine Straße auf die Karte zeichnen, wenn Du "Straße erstellen" anklickst. Die Straßen, die Du erstellen kannst, zeigt der Streckenverlauf rot an. Erstelle keine Segmente über bereits bestehende Straßen. Schau Dir zuerst die Karte an! </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Gebiete=== Diese Liste zeigt definierte Gebiete an, in denen Du arbeiten kannst. Entweder die Gebiete, die Du befahren hast oder die Gebiete in denen Du Area- oder Country-Manager bist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Segmente== [[File:Reiteranzeige.png|right]] [[File:Ausgewaehlt editmodus.png|right]] '''Einzelnes Segment ausgewählt:'''<br> Im oberen Teil werden der Name des Segments und die "Alternativen Straßennamen" angezeigt. Darunter der Bearbeiten-Button. Im unteren Teil wird Straßentyp, Richtung, Ebene und Stufe der Sperre angezeigt. '''Bei Mehrfach-Auswahl:'''<br> Der obere Bereich zeigt an, wie viele Segmente ausgewählt sind. Das Beispiel rechts zeigt, wie die Situation aussieht, wenn 2 Segmente ausgewählt sind im "Bearbeiten-Modus". '''Eigenschaften bearbeiten:'''<br> Wenn Du auf Bearbeiten klickst oder das Tastaturkürzel '''"e"''' drückst, wechselt die Ansicht in den Bearbeiten-Modus und zeigt alle wichtigen Informationen an. Es ermöglicht Dir alle Eigenschaften wie: Landes-, Stadt- und Straßennamen zu ändern. Das Feld für Bundesländer/Kantone resp. Staaten ist im Moment noch den USA vorbehalten. Auch alternative Straßennamen kannst Du bearbeiten. Dies ist dann interessant, wenn die Straße einen lokalen Namen besitzt, der nicht im Hauptfeld des Segments Platz hat, oder nicht offiziell gebräuchlich ist. Beispiel: Die A1 in Österreich hat im alternativen Namen die Bezeichnung "West Autobahn" Oder das Beispiel, das im Screenshot zu sehen ist.<br> '''Das Stadt-Feld des alternativen Namens muss den selben Namen, wie das Stadt-Feld des Segments besitzen.''' <br style="clear: both" /> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ausgewählte Orientierungspunkte== {| border="0" cellpadding="2" style="background:none;" |- style="vertical-align:top;" |Wenn Du eine Orientierungspunkt auswählst, kannst Du ihn benennen, einen Orientierungspunkt-Typ vergeben und den Orientierungspunkt mit einer Sperre versehen. Die Sperre hindert Editoren mit niedrigeren Stufen (Rechte) den Orientierungspunkt zu verändern: | |Darunter befinden sich die Adressdetails. ''Klick'' auf '''Bearbeiten''' und ändere die Details, ''klick'' auf '''Übernehmen''', wenn Du alles eingegeben hast: |- style="vertical-align:top;" |[[File:Orientierungspunktausgewaehlt.png]] | |[[File:Orientierungspunktausgewaehltadressdetails.png]] Wird eine korrekte Adresse eingegeben, ermöglichen wir damit Waze, die interne Suche für die Orientierungspunkte zu verwenden und nicht externe Anbieter. |} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Anzeigebereich der Karte= Alle ausgewählten Ebenen sind im Anzeigebereich der Karte zu sehen. Der Anzeigebereich der Karte nimmt den Hauptteil des Browser-Fensters ein. Jedes Objekt, das angezeigt wird ist auswählbar und kann bearbeitet werden. Dies hängt von den Rechten ab, die Du im ausgewählten Kartenausschnitt besitzt. Wähle eine Straße aus und verändere ihre Geometrie. Wähle einen Orientierungspunkt aus und gebe ihm einen Namen. Füge eine Straße hinzu, wo eine sein sollte oder lösche Straßen, die nicht mehr zu sehen sein sollen. Es gibt sieben Hauptbestandteile in den Ecken des Anzeigebereichs auf der Karte: #Die Infoleiste #Die Zoom-Steuerung inkl. Streetview #Die Schaltfläche für den Chat #Die Ebenen-Auswahl #Die Permalink-Schaltfläche #Die Anzeige des Längen- und Breitengrades #Die Zoom-Skala </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Info Leiste== [[File:Infoleiste.png|700px]] Unter dem Suchfeld befindet sich die Info-Leiste. *Links die Stadt und das Land des aktuellen Kartenausschnitts. *Rechts befindet sich eine Box, die nur erscheint, wenn etwas geladen wird. Karte lädt, Speichern, Straßen laden etc. Daneben die Ebenen-Auswahl. Probleme beim Speichern können hauptsächlich beim Verbinden an Kreuzungen und Geometrieänderungen entstehen. Deshalb arbeite sorgfältig, und Du ersparst dir Mehraufwand. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Zoom-Steuerung== [[Image:Zoomregler.png|left]] Tastaturkürzel: '''Shift+UpArrow''', Tastaturkürzel: '''Shift+DownArrow''' In der oberen linken Ecke befindet sich die Zoom-Skala, sie besitzt 10 Stufen. Die Steuerung der Skala + und - kann benutzt werden, um die Karte zu vergrößern oder zu verkleinern. Dies funktioniert auch, wenn der Regler verschoben wird, oder am einfachsten, wenn man am Mausrad dreht. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Streetview== [[Image:Streetview.png]] Direkt unter der Zoom-Steuerung befindet sich der Streetview. Ziehe die blaue Linse auf die Straße, die Du im Streetview anschauen möchtest. Der Streeview ist nicht überall vorhanden, er hängt davon ab, was uns Google zur Verfügung stellt. [[Image:Streetview-nicht-vorhanden.png|left]] Wo kein Streetview verfügbar ist, bleibt die Linse beim Ziehen über der Karte rot. <br style="clear: both" /> [[Image:Streetview-vorhanden.png|left]] Wo der Streetview verfügbar ist, färbt sich die Linse beim Ziehen über der Karte blau, Du kannst die Linse loslassen und die Straße im Streetview anschauen. <br style="clear: both" /> Wenn Du die Linse losgelassen hast, enthält sie einen Pfeil, der in die Richtung des Streetviews zeigt. [[Image:Wme streetview directional arrow.gif]] Während des Streetviews sind alle anderen Operationen möglich (Segment-Eigenschaften, Kartenfehler und Aktualisierungsanfragen, Hausnummern, zeitliche Beschränkungen etc.) Die Rechte Seite des Fensters enthält den Streetview. Du kannst die Ansicht in alle Richtungen verschieben mit der Maus, oder mit der Steuerung oben links im Streetview-Fenster. Zoomen kannst Du über den Regler oder mit dem Mausrad. Um die Position der Ansicht zu verschieben, kannst Du auf die Pfeile unterhalb der Bildmitte klicken oder Dich per Mausklick fortbewegen. Du kannst auch die Linse auf der Karte verschieben, mit dem kleinen weißen Punkt darunter. [[Image:Streetview-situation.png|700px]] Wenn Du zu viel auf einmal aktivierst, wirst Du feststellen, dass der bearbeitbare Bereich auf der Karte immer kleiner wird. Z.B. eine Aktualisierungsanfrage mit dem Fenster für Kommentare. Denke an die Tastaturkürzel, denn der Zoom-Regler der Karte ist dann verdeckt und somit kannst Du nur noch mit den Tastaturkürzeln Zoomen. Um den Streetview zu beenden, klicke auf das X in der oberen, rechten Ecke des Streetview-Fensters. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Der Editor-Chat== Wird demnächst erstellt </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Ebenen-Auswahl== Auf der rechten Seite der Karte findest Du dieses Symbol: [[Image:Layers-Auswahl.png]] Wenn Du mit der Maus darüber fährst, zeigt es Dir an, welche Ebenen aktuell ausgewählt sind. Die Ebenen mit den vier Punkten vor dem Namen, kannst Du in der Auswahl beliebig anordnen. [[WME_Schnellstart-Anleitung#Tastaturk.C3.BCrzel|'''Tastaturkürzel''']]. [[File:Ebenen.png]] Hier ein paar Informationen dazu. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Die Luftaufnahmen=== [[Image:Aerial_skinny.png|260px]] Tastaturkürzel: '''Shift+b''' Waze benutzt Luftaufnahmen von Google (oder VirtualEarth). </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Städte=== [[Image:cities_skinny.png|260px]] Tastaturkürzel: '''Shift+c''' Diese Ebene zeigt die Grenzen der Städte verschiedenfarbig an in Form von Polygonen. Je nachdem, wie die Segmente benannt wurden. Dies ist hilfreich, um falsch benannte Segmente zu identifizieren. Manchmal können die Grenzen überlappen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Straßen=== [[Image:Road_segments_skinny.png|260px]] Tastaturkürzel: '''Shift+r''' In der Ebene sind die Straßen, Gassen, Autobahnen etc., aus denen sich die fahrbare Karte des Systems in Waze zusammensetzt. Je nach Zoom-Stufe sind einige Straßen nicht sichtbar, damit die Karte nicht zu unübersichtlich dargestellt wird. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===GPS-Punkte=== [[Image:Gps_tracks_straight_skinny.png|260px]] Tastaturkürzel: '''Shift+g''' Diese Ebene zeigt die GPS-Punkte der Benutzer an, die mit der Waze-App herumgefahren sind. Waze zeichnet die GPS-Koordinaten der Fahrer auf und wandelt sie in farbige Pfeile um, diese sind dann in der Karte sichtbar. Diese Ebene ist sehr hilfreich, um Straßen auf der Karte an richtiger Stelle zu platzieren, wenn z.B. keine Luftbilder vorhanden sind. Die Pfeile haben unterschiedliche Farben in jeder Fahrtrichtung. Das macht es einfacher, fehlerhafte GPS-Spuren zu lokalisieren oder Straßen auf der Karte zu finden, die nicht dem tatsächlichen Straßenverlauf folgen. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Area-Manager=== Zeigt die Area-Manager im ausgewählten Ausschnitt an. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Orientierungspunkte=== [[Image:Landmarks_skinny.png|260px]] Tastaturkürzel: '''Shift+l''' Orientierungspunkte sind auch unter Landmarks oder POI's (Points of Interest) bekannt. Diese können für nahezu alles verwendet werden: Tankstellen, Parks, Flüsse. Friedhöfe etc. Mehr Informationen zu den Orientierungspunkten findest Du [[Erstellen und bearbeiten von Landmarks|hier]]. </noinclude></noinclude> </noinclude> </noinclude> </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Kartenfehler=== [[Image:Problem_pin_open-low.gif|left]][[Image:Problem_pin_open-med.gif]] [[Image:Problem_pin_open-high.gif]] Tastaturkürzel: '''Shift+p''' <br> Der Waze-Server analysiert laufend die GPS-Daten, um Fehler zu erkennen. Diese werden dann über die Ebene Kartenfehler sichtbar. Sie sollen den Benutzer, der die Karte bearbeitet darauf hinweisen, dass die Karte Fehler aufweist, die es zu bearbeiten gilt. Typische Kartenfehler sind: Fehlende Straßen, falsche Abbiegungen, falsche Einbahnstraßen oder fehlende Verbindungen zwischen Segmenten. Für Informationen, lies [[WME Map Problems]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Aktualisierungsanfragen=== [[Image:Request_pin_open-low.gif|left]][[Image:Request_pin_open-med.gif]] [[Image:Request_pin_open-high.gif]] Tastaturkürzel: '''Shift+u''' <br> Die Aktualisierungsanfragen werden von den Benutzern der Waze-App während der Fahrt oder auf der "Echtzeit-Karte" gemeldet. *Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei gefahren ist, zeigt die Ebene im Karteneditor hellgrün an. *Die Strecke vor und nach der Aktualisierungsanfrage, die der Benutzer dabei während der Navigation gefahren ist, zeigt die Ebene im Karteneditor lila an mit den Abbiege-Anweisungen, die der Benutzer dabei erhalten hat. *Für Informationen, lies [[WME Update Requests]]. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ===Meine Gebiete=== [[Image:Editable_area_skinny.png|260px]] Tastaturkürzel: '''Shift+e''' Wo Du die Karte bearbeiten kannst, hängt davon ab, wo Du mit der Waze-App gefahren bist. Die Rechte sind im Umkreis von 1 Meile bzw. 1,6 Kilometer um die befahrene Strecke vorhanden. Die Gebiete die Du bearbeiten kannst, zeigen sich im Karteneditor wie folgt: *Hell hinterlegt sind Gebiete, die Du mit Waze befahren hast. *Die farbigen Gebiete sind die, in denen Du Area-Manager bist. *Dunkle Gebiete kannst Du nicht bearbeiten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Permalink-Schaltfläche== [[Image:Permalink-neu.png]] Außerhalb der Karte unten rechts befindet sich die Permalink-Schaltfläche. Der Permalink ändert immer dann, wenn die Karte verschoben wird, Objekte ausgewählt oder deselektiert werden. Man beachte: Der Permalink wird nicht jedesmal automatisch neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn man eine Browser-Sitzung wiederherstellt inkl. Editor, wird der Browser die letzte Kartenposition des Permalinks anzeigen, den man zuvor generiert hat. Wenn man Permalink anklickt, speichert dieser alle Informationen für den ausgewählten Kartenausschnitt. Man kann ihn anklicken, um die Karte zu aktualisieren, mit einem Rechtsklick kopieren, mit anderen Benutzern im Forum teilen oder als Lesezeichen ablegen. Vor allem bei Fragen zur Karte wird der Permalink im Forum oft gebraucht. Denn er speichert auch ausgewählte Straßen, Kreuzungen und Landmarks, so zeigt er anderen Benutzern schnell, was gemeint ist. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Anzeige des Längen- und Breitengrades== [[Image:Koordinaten.png]] In der unteren rechten Ecke befindet sich die Anzeige des Längen- und Breitengrades. Sie zeigt den aktuellen Ort, wo der Mauszeiger gerade hinzeigt. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> ==Die Zoom-Skala== {| style="float:left; background: transparent;" width="400" |[[Image:Zoom-Skala.png|left]] |- |Unten rechts befindet sich die Anzeige der Zoom-Stufe. Die Werte in der Skala rechts entsprechen auch der [[#Zoom-Steuerung | Zoomstufe]], die Du in der URL des Browsers siehst (zoom=5). Änderst Du die Zoomstufe darin, verändert sich auch die Ansicht. |} {| style="float:right;" |[[Image:Stufenscala.png]] |} {{Clear}} </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karteneditor Steuerung= *Bewege die Karte, indem Du sie mit der Maus umherziehst. *Mit den Pfeiltasten kannst Du die Karte in alle vier Richtungen verschieben. *Es gibt vier Möglichkeiten die Karte zu zoomen: #Über die Zoom-Steuerung am linken oberen Rand der Karte. Regler hoch oder runterziehen mit der Maus oder klicke auf die + oder - Buttons. #Ein Doppelklick auf der Karte zoomt die Karte um eine Stufe rein und zentriert den Ausschnitt an den Ort, wohin man geklickt hat. #Am Mausrad drehen. Zurückdrehen, um zu verkleinern, nach vorne drehen, um zu vergrößern. Auf dem Mac mit einem Trackpad oder ähnlichem, nach links und rechts ziehen bewirkt das selbe. #Die ''Shift'' Taste drücken und ein Rechteck auf der Karte Zeichnen. Die Karte zoomt den ausgewählten Auschnitt ein: [[Image:Shift_zoom.png|500px|center]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =WME Schnell-Start Anleitung= Der Karteneditor wurde sehr intuitiv gestaltet, damit man ohne viele Dokumentationen zu lesen, sofort damit arbeiten kann. Um die besten Techniken zu kennen und anzuwenden, braucht ein bisschen Zeit. Aber es kann auch Spaß machen mit wachsender Erfahrung. Man kann Stolz sein darauf, die Anwendung mit ein paar einfachen Bearbeitungsschritten für alle Endbenutzer zu verbessern. Die Links später in dieser Anleitung sind sehr wichtig, um alles zu erlernen was es braucht. Für die einfache Bearbeitung gibt es hier die [[WME Schnellstart-Anleitung]] um sich schnell zurecht zu finden. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Der Permalink= :[[Image:wme permalink highlight.jpg]] *Im Karteneditor ist der [[Glossar#Permalink|Permalink]] eine URL, die Dich direkt an einen spezifischen Punkt auf der Karte bringt. Er speichert Längen- und Breitengrad, Zoom Stufe und alle Sichtbaren Objekte die während der Bearbeitung aktiv sind auf der Karte (ausgewählt in den Ebenen). Um genau auf ein Problem hinzuweisen sollte das betreffende Objekt ausgewählt sein, dies wird nämlich auch gespeichert. *Nach dem Klick auf Permalink unten rechts im Karteneditor, findest Du die Adresse zum Link in der Adresszeile des Browsers. Diese kann kopiert und in Foren-Beiträgen oder Lesezeichen eingefügt werden. Dies funktioniert auch wenn Du Permalink mit der rechten Maustaste auswählt und die Adresse direkt kopierst. *Hinweis: Der Permalink wird nicht jedesmal neu generiert, wenn man den Kartenausschnitt mit der Maus verschiebt. Wenn Du eine Browser Sitzung wiederherstellst inkl. Editor, wird der Browser die letzte Karten-Position des Permalinks anzeigen, den Du zuvor generiert hast. *Falls die Straßen nicht mit den Luftaufnahmen übereinstimmen oder eine ungewöhnliche Position aufweisen, kannst Du mit dem Permalink die Seite aktualisieren, was das Problem in der Regel löst. *Was andere Editoren im Permalink sehen können, hängt von den Rechten ab, die sie besitzen. Ein Editor kann Aktualisierungsanfragen (Update Requests) oder Kartenfehler (Map Problems) nur in seinem bearbeitbaren Gebiet sehen. Also die lokalen Editoren, Area-Manager oder Country-Manager der betreffenden Gebiete oder Länder. Wenn Du ein breiteres Publikum betreffend eines Problems erreichen willst, musst Du ein Bildschirmfoto posten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Permalink in der Echtzeitkarte= Willst Du einen Permalink in der Echtzeitkarte generieren, musst Du auf die Permalink-Schaltfläche in der unteren, rechten Ecke der Karte klicken. Routen werden dabei auch gespeichert. *[[Image:PermalinkLiveMap.png]] </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Tastaturkürzel= Der Einfachheit halber sind alle Kürzel im [[WME_Schnellstart-Anleitung#Tatstaturk.C3.BCrzel|WME Schnellstart-Anleitung]] an einem Ort zusammengefasst. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Karten Aktualisierung= Alles was bearbeitet wurde mit dem Karteneditor, wird früher oder später auf der Live Map und in der Waze-App zu sehen sein. Das Ziel von Waze ist es, alle Daten innerhalb von 24 Stunden zu aktualisieren. Dies kann auch mal länger dauern, schau Dir deshalb auch die Seite [[Ablauf der Aktualisierungsprozesse|Ablauf der Aktualisierungsprozesse]] an. *Die Aktualisierungen und sonstige Ereignisse, werden auch auf der [http://status.waze.com/ Status-Seite] von Waze publiziert. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> =Einsatz von externen Quellen (wie Google Imagery)= Die Verwendung von beliebigen externen, urheberrechtlich geschützten Informationsquellen, um Informationen in die Datenbank oder die Waze-Karten einzupflegen, ist nicht erlaubt. Externe urheberrechtlich geschützte Informationsquellen beinhaltet alle Online- oder gedruckten Karteninformationen, die nicht von Waze durch die Schnittstelle des Karteneditors bereitgestellt werden. Mit der Akquisition von Waze durch Google, Inc., wurde der Karteneditor von Waze mit Luftaufnahmen von Google und dem Streetview aktualisiert. Diese gelten als interne Quellen und dürfen daher verwendet werden, um Karteninformationen zur Waze-Karte hinzuzufügen. Googles Nutzungsbedingungen binden die Nutzung ihrer Karteninformationen an spezifische Bedingungen und Waze besitzt nur die ordnungsgemäße Lizenz, das was im Karteneditor zu sehen ist auch zu nutzen, aber sonst nichts anderes von Google. Die Verwendung von externen, urheberrechtlich geschützten Quellen gefährden die Karten und Waze wird dadurch gezwungen, alle Änderungen zu löschen und den Urzustand der Karte wieder herzustellen. Dies betrifft alle Änderung des betreffenden Benutzers auf der ganzen Karte! Wenn Du Karten in der Form erstellst, sieht sich Waze leider gezwungen, Deine ganze Arbeit von der Karte zu löschen. So ist es bereits in Chile und anderen Südamerikanischen Ländern passiert aufgrund der Lizenzprobleme. (kein Fehler seitens Waze!) Du darfst gerne mit lokalen Anbietern oder Behörden kommunizieren um allf. Luftaufnahmen oder Informationen zu erhalten, die verwendet werden dürfen. Du musst allerdings dabei klar erwähnen, dass Du nicht für Waze arbeitest oder in Auftrag von Waze handelst. Aber als interessierter Bürger kannst Du natürlich mit den lokalen Behörden sprechen, um die Vorteile für die Allgemeinheit zu erklären, z.B Luftaufnahmen als öffentliches Gut frei zur Verfügung zu stellen. Bei Fragen oder wenn Du nicht sicher bist, kommuniziere unbedingt mit dem Waze-Support. Beachte, dass externe Urheberrechtsinformationen keine Informationsquellen beinhalten, die von Waze durch die internen Werkzeuge des Karteneditors oder der Waze-App zur Verfügung gestellt werden. Auch alle Informationen, die selbstständig von einem Benutzer entwickelt wurden und physisch an einer Stelle abrufbar sind, werden akzeptiert, um damit die Karte zu bearbeiten, solange es nicht urheberrechtlich geschützt zur Verfügung gestellt wurde. Du darfst mit dem Support reden, wenn Du eine Quelle benutzen möchtest und nicht sicher bist, ob Du sie auch verwenden darfst. Waze wird die Quelle prüfen und Dir mitteilen, ob Du sie verwenden darfst oder nicht. Wenn nicht klar ist, ob eine Verwendung Legal ist, gelten die nachfolgenden Verbote. '''Folgendes ist Verboten:''' *Nachschauen ob der Straßenname korrekt ist. *Straßennamen von anderen Karten abtippen. *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren (manuell). *Neue Straßen von anderen Karten hinzufügen, den Verlauf kopieren mit einem Skript. '''Es ist sehr einfach:''' *Verwende den Karteneditor mit den Möglichkeiten, die innerhalb Waze angeboten werden. *Vermeide alles andere, sofern nicht geprüft und bestätigt von Waze. Darum zeigt Waze im Karteneditor nur die Streetview Bilder ohne zusätzliche Daten. </noinclude><center><small>[[#Top|Zurück zum Anfang der Seite]]</small></center> <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] 26ee5b3bc206ae30040a2f37981fe43937031380 0 108 12126 2021-10-03T22:28:58Z Popel22 24 Die Seite wurde neu angelegt: «[[germany:Anleitung_zum_Bearbeiten_der_Karte|Zurück zur Anleitung]] ==Bearbeitung ohne Anzeige der Straßen== Du kannst Straßen und Kreuzungen auch bearbeiten…» wikitext text/x-wiki [[germany:Anleitung_zum_Bearbeiten_der_Karte|Zurück zur Anleitung]] ==Bearbeitung ohne Anzeige der Straßen== Du kannst Straßen und Kreuzungen auch bearbeiten, wenn die Anzeige in der Straßen-Ebene ausgeschaltet ist. Wenn der Luftbild-Layer angeschaltet ist, siehst Du immer noch die Karte. Wenn Du über die verborgenen Straßen fährst mit der Maus leuchten diese auf. Das Gleiche gilt für Kreuzungen. So kannst Du zum Beispiel bequem Straßen an die Karte anpassen oder die GPS-Punkte, wenn der GPS-Layer angeschaltet ist ==Geometrie-Punkte schnell entfernen== Wenn ein Segment ausgewählt ist, bewege die Maus auf die Straße, um die Geometrie-Punkte sichtbar zu machen. Wenn Du einen der Punkte mit der Maus berührst kannst Du ihn mit der Taste [D] löschen. Wenn Du die [D]-Taste gedrückt hältst, kannst Du mit der Maus einfach der Straße entlang fahren, um alle Geometrie-Punkte zu löschen. Dies funktioniert auch bei POI, die als Fläche angelegt sind und bei Kartenkommentaren. ==Straßen ohne Namen und Stadt erfassen== *Um Straßen ohne Stadt und Straßennamen zu erfassen, musst Du das Kontrollkästchen "Ohne" für diese Felder benutzen. In Deutschland bekommen alle Straßensegmente einen Gemeindenamenseintrag! Einzige Ausnahme bilden die Bundesautobahnen und daran anschließende Rampen für Auf- und Abfahrten der BAB. *Neu gezeichnete Straßen können zwar gespeichert werden, bleiben aber rot auf der Karte und werden nicht auf der App erscheinen oder fürs Routing in Betracht gezogen. *Eine neu gezeichnete Straße darf nicht mit sich selbst verbunden werden, Du musst ein zusätzliches Segment oder eine Kreuzung hinzufügen. Ansonsten kann es zu Fehlern beim Berechnen von Routen kommen. ==Geometrie Änderungen bei Mehrfach-Auswahl== Du kannst auch mehrere Straßen auswählen und die Geometrie verändern. Fahre einfach mit der Maus auf die Straße, die Du gerade verändern möchtest. Die Auswahl der anderen Straßen bleibt bestehen. ==Verschieben von Segmenten über die Grenze des Möglichen== Wenn Du das Ende eines Segments zuweit von seinem Start- oder Endpunkt aus verschiebst, wird die Fehlermeldung erscheinen: Das markierte Element wurde über die zulässige Distanz hinaus verschoben. Bitte prüfen und erneut versuchen." Möglichkeiten um dies zu umgehen: *Verschiebe das Segment nur ein wenig und speichere zwischendurch. *Teile das Segment in mehrere Teile auf. *Zeichne ein neues Segment, dieses kannst Du so weit in die Länge ziehen, wie Du willst. <br /> ==Städte-Polygone== Die Städte-, Orts- oder City Polygone enthalten oder umfassen ca. 90-95% aller Straßen, denen der gleiche Stadtname zugeordnet ist. Waze entfernt etwa 5-10% der farbigen Fläche im WME, um grössere Überlappungen zu vermeiden und eine saubere Darstellung zu gewährleisten. Bei der Benennung von neuen Segmenten beträgt der Radius 25 Kilometer zum bestehenden Polygon. Wird ein bereits existierender Stadtname weiter als 25 Kilometer entfernt hinzugefügt erscheint die Meldung: "Die markierte Straße ist zu weit von der zugehörigen Stadt entfernt." [[germany:Anleitung_zum_Bearbeiten_der_Karte|Zurück zur Anleitung]] 26c9d989383246d5fe50eea91dd632a0f492c9c8 8 109 12128 2022-12-01T17:29:20Z Maintenance script 107 wikitext text/x-wiki File uploads are disabled for all the local community wikis. Please upload your files to the [https://wazeopedia.waze.com/wiki/Commons/Special:Upload main file repository]. 90bfeb8c0119d2ff36f07a275fa0747573e22538 0 12 12129 12124 2022-12-06T18:37:27Z Thalibahn 73 wikitext text/x-wiki Diese Seite gibt eine Übersicht der Funktionsträger der DACH-Länder Deutschland, Österreich und Schweiz. ==Verwendete Abkürzungen== '''GC''': Global Champ<br> '''LC''': Local Champ<br> '''CM''': Country Manager '''SM''': State Manager<br> '''AMS''': Autonomous Management System (deutsch: Selbstverwaltung)<br> '''SME''': Social Media Expert<br> '''PM''': Personal Message / Persönliche Nachricht<br> '''E''': Eremitierter GC <br /> ==Schweiz== {| class="wikitable sortable center" |- !User!!Edit-Level!!Koordinator!!GC!!LC!!CM!!AMS!!SME !SM!!PM |- |- |popel22||6||X||X||X||X||X|| | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=10838409 PM] |- |vince1612||6|| ||X||X||X||X||X | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=14731619 PM] |- |pjw65||6|| || ||X||X||X||X | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=1558432 PM] |- |Athannor||6|| || ||X||X||X|| | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17430174 PM] |- |cedricvondk||5|| || || ||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=17132115 PM] |- |''Mal0ne'' <span style="color:#606060">''<small>(Inaktiv)</small>''</span> |5|| || || ||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=16781303 PM] |- |MattKo||6|| || ||X||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=282530 PM] |- |''pikifoo'' <span style="color:#606060">''<small>(Inaktiv)</small>''</span> |3|| || || ||X|| || | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=330174 PM] |- |''Blizteam'' <span style="color:#606060">''<small>(Inaktiv)</small>''</span> |4 | | | | | | |x |[https://www.waze.com/forum/user_message_redirect.php?username=blizteam PM] |- |GeoCord |4 | | | | | | |x |[https://www.waze.com/forum/user_message_redirect.php?username=GeoCord PM] |- |Messanger |4 | | | | | | |x |[https://www.waze.com/forum/user_message_redirect.php?username=messanger PM] |- |svx-biker||6|| ||E||X||X||X|| | ||[https://www.waze.com/forum/ucp.php?i=pm&mode=compose&u=3354006 PM] |- |<span style="color:#606060">''argus-cronos<br /><small>(Inaktiv)</small>''</span>||<span style="color:#606060">''6''</span>|| || ||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span>||<span style="color:#606060">''X''</span> | || |} ==== [[germany:Organisation_Deutschland|Seite für Deutschland]] ==== e9f79041c9218841138a22bfa80dac85f5029597 0 14 12130 12081 2023-04-18T12:39:25Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. '''Fusswege dürfen ans Strassennetz angeschlossen werden.'''[[Datei:Fusswege mit "Ghost-Nodes".jpg|miniatur|403x403px|ohne]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone[[Datei:WTvsPB.png|miniatur|518x518px|ohne]] (PB = Fussgängerzone / WT = Fussweg) == '''FUSSWEGE''' N == <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ===Ein Tipp=== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] bbae151bbcbbdc063101196a56736473530cd770 12132 12130 2023-04-18T12:46:21Z Popel22 24 wikitext text/x-wiki [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] Hier findest Du wichtige Informationen in Zusammenhang mit Fußwegen und Privatstraßen. Um Probleme bei der Navigation zu vermeiden, gilt es ein paar Vorkehrungen zu treffen auf der Karte. Wann immer Du im [[Häufig_gestellte_Fragen#Was_ist_der_Waze_Map-Editor.3F|Karteneditor]] eine Straße bearbeitest, die von der Norm abweicht (Gesetze, Hindernisse, Größe etc.), denke darüber nach, ob und wie eine Straße von der Allgemeinheit (Pendlern/PKWs) befahren werden darf. '''Fusswege dürfen ans Strassennetz angeschlossen werden.'''[[Datei:Fusswege mit "Ghost-Nodes".jpg|miniatur|403x403px|ohne]] Beachte bitte folgende Grafik bei der Auswahl Fussweg / Fussgängerzone[[Datei:WTvsPB.png|miniatur|518x518px|ohne]] (PB = Fussgängerzone / WT = Fussweg) == '''FUSSWEGE''' == <br> '''Fußwege werden nur in Ausnahmefällen eingezeichnet.''' '''Gründe, wieso ein Fußweg auf der Karte erscheinen soll:''' * Der Fußweg hat einen Namen * Der Fußweg hat einen Namen, der Aufgrund der Adresse bedeutend ist * Der Fußweg hat einen Namen und bedient Grundstücke, oder dient der Orientierung bei größeren Gebäuden mit mehreren Eingängen Bei all den genannten Gründen musst Du Dir trotzdem Gedanken darüber machen, welche Auswirkungen die Fußwege auf das Routing haben. Zeichne keine unnötigen Fußwege ein! Im Folgenden ein paar Beispiele, um Dir die Sache ein wenig zu erleichtern. ===Ein Tipp=== Halte die Karte einfach (Keep it simple and stupid! = KISS), vermeide [[Die_beste_Vorgehensweise_beim_Bearbeiten_der_Karte#Unn.C3.B6tige_Kreuzungen|unnötige Kreuzungen]] auf dem Straßennetz und versuche mögliche Fehlerquellen zu eliminieren. Verschwende nicht Deine wertvolle Zeit mit unnötigen Edits, wie Richtungen bei Fußwegen. Ein Fußweg hat keine Fahrtrichtung, denn wir fahren nicht darauf. Unnötige Fußwege sollten nicht eingezeichnet werden. =Privatstraßen= Bei allen möglichen Situationen, die Du auf der Karte antriffst, musst Du als Editor definieren, ob eine Einfahrt, Durchfahrt oder eine Route aus einer Straße heraus möglich sein soll. Dies richtet sich in der Regel nach baulichen Gegebenheiten oder gesetzlichen Vorgaben. Und zuletzt natürlich nach den Möglichkeiten, die wir mit dem Karteneditor haben. '''Die "Privatstraße" besitzt folgende Eigenschaften:''' <br> * Eine Route in eine Privatstraße ist möglich * Eine Route aus einer Privatstraße heraus ist möglich * Eine Route durch eine Privatstraße hindurch ist '''nicht''' möglich Folglich ist die Privatstraße unser bester Helfer, um eine befahrbare Straße von der Routenplanung auszuschließen.<br> '''Verwendung der Privatstraßen''' * Beschilderte Privatstraßen * Alle Straßen, die nicht für den allgemeinen Verkehr freigegeben sind * Feldwege, die nur für Forst- oder Landwirtschaftlichen Verkehr zugelassen sind * Jegliche Straßen die nur für Zubringer, Anrainer, Anstösser, Lieferanten (auch nur zeitweise) etc. erlaubt sind Bei allen Arten von Privatstraßen sind die Abbiegepfeile korrekt zu definieren. Es macht keinen Sinn, Abbiegungen in Privatstraßen zu verbieten, da so Berechtigte vom Routing ausgeschlossen werden. Auch jegliche andere Späße, wie zusätzliche Kreuzungen, "unbekannte" Fahrtrichtung oder unterteilen durch andere Straßentypen etc. sind vollkommen unnötig! ==Beispiel Poller oder Barriere== Hier ein Thema, das immer wieder für Verwirrung sorgt und wofür es auch auf der Waze-Karte leider die verschiedensten Ideen gibt, wohlgemerkt nicht immer die Besten! Es dreht sich um versenkbare Automatikpoller oder Analog dazu "Barrieren" mit der selben Funktion. Das denkbar schlechteste Beispiel ist dieses hier: [[File:Poller-falsch.png|center|frame|Poller auf Abwegen, abgetrennt durch einen Fußweg.]] <br> Stell Dir vor, Du bist berechtigt in dieser Straße zu fahren. Du stehst vor dem Poller, planst eine Route und drückst die Fernbedienung für das Absenken des Pollers. Du schaust auf die App und siehst, dass die geplante Route in die falsche Richtung läuft?!? Der Grund sollte klar sein, der Fußweg dazwischen wird "normalerweise" vom Routing ausgeschlossen. Was denkst Du über Waze? Wirst Du wenden und zurückfahren oder gar Rückwärts deiner geplanten Route folgen? Solche Situationen sind vielleicht selten, ich gebe Dir auch Recht, dass Waze die Route neu berechnen wird, sobald Du den Fußweg entgegen der Route überfahren hast. Dennoch es ist komplett unnötig, spar Dir das Gebastel auf der Karte! Der Poller oder die Barriere muss nicht optisch dargestellt werden, nicht mit beschrifteten Segmenten und schon gar nicht mit Orientierungspunkten. Damit müllt man nur unnötig die Karte zu. Hier die korrekte Lösung: [[File:Poller-richtig.png|center|frame|Privatstraße mit korrekten Abbiegeregeln.]] <br> * Eine normale Privatstraße * Sie wird von Berechtigten verwendet und alle anderen Fahrer erhalten keine Route durch diese Straße * Die Straße hat einen Namen und heißt nicht Poller oder Barriere * Die Abbiegungen sind natürlich individuell zu betrachten und richten sich nach der jeweiligen Situation * Es entstehen keine Kartenfehler * Du steigerst weder den Server-Verkehr noch den Datenverkehr der App unnötig, indem Du auf Landmarks und sonstige nutzlose Optik verzichtest <br> [[Anleitung zum Bearbeiten der Karte|Zurück zur Anleitung]] [[Category:Anleitung]] bbad993589b0bd92b31cab8f2e17f0c286d93069 14 110 12131 2023-04-18T12:39:25Z Automatische Kategorienerstellung 141 Automatisch von der AutoCreateCategoryPages-Erweiterung erstellt. wikitext text/x-wiki Dies ist eine Kategorieseite. Sie listet alle Seiten in der Kategorie „Anleitung“ sowie alle Unterkategorien der Kategorie „Anleitung“, sofern welche vorhanden sind. b351c7443a2c770d7d937f9973fc4c2e76aefea8